21788
Updated**Remediation action**
Daily.Entra.NewsAll 20 supplied records are Microsoft Learn updates. There are no new or removed records and no Message Center notices. The meaningful edits are guidance and reference changes: the Manage DNS page warns against zone-level redirection for windowsazure.com and core.windows.net; Conditional Access documentation clarifies log interpretation; Graph troubleshooting calls out email-validation sign-up failures; and Global Secure Access documents an application-discovery workflow. The evidence supports no claim of a new feature, preview, general availability, retirement, or changed runtime behavior. The External ID Cloudflare-integration update has no summary, so it cannot support a more specific claim.
The updated Manage DNS guidance says not to redirect DNS zones related to windowsazure.com or core.windows.net. If redirection is required, it says to limit it to individual host names—for example, server1.file.core.windows.net rather than file.core.windows.net. This is explicit networking guidance, not evidence of a new enforcement mechanism.
The updated Sign In Log Activity Details page defines Success as the Conditional Access policy being applied successfully to the sign-in attempt. This is a documentation clarification for interpreting existing sign-in records; the evidence does not indicate that Conditional Access evaluation changed.
The updated How to Analyze Activity Logs with Microsoft Graph guide calls out how to find sign-up attempts that failed during email validation. This provides troubleshooting coverage for a specific failure path, but the record does not indicate changed sign-up behavior or a new rollout.
The updated Application Discovery for Global Secure Access page says to use Application discovery to detect applications accessed by users and create separate private applications. It documents a capability workflow; the supplied evidence does not establish whether this is new, in preview, or generally available.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
**Remediation action**
**Remediation action**
**Remediation action**
**Remediation action**
A Microsoft Entra documentation page was updated: Customer intent: As an IT admin, I want to learn how to troubleshoot sign-up errors for various scenarios and using different tools so that I can resolve sign-up issues quickly..
A Microsoft Entra documentation page was updated: Audit Logs.
> [!IMPORTANT]
A Microsoft Entra documentation page was updated: Sign Ups.
- **Success:** The Conditional Access policy was applied successfully to the sign-in attempt.
- Provectus - Secure Contacts
We're continually adding more administrative portals to the list.
Before you configure a forest trust in Domain Services, make sure your networking between Azure and on-premises environment meets the following requirements:
Refrain from redirecting DNS zones related to windowsazure.com or core.windows.net. If DNS redirection is required, limit the redirection to individual host names instead of zones. For example, use server1.file.core.windows.net instead of file.core.windows.net.
A Microsoft Entra documentation page was updated: Sign Ins.
Welcome to what's new in the Microsoft identity platform documentation. This article lists new articles that were added or had significant updates in the last three months.
- To find sign-up attempts that failed during email validation:
Use Application discovery to detect the applications accessed by users and create separate private applications.
For information about connectors, capacity planning, and how they stay up-to-date, see [Understand Microsoft Entra private network connectors](concept-connectors.md).