Daily.Entra.News25 changes were tracked across 6 Microsoft Entra products. The leading updates include Microsoft Entra ID: Retirement of duplicative properties in passkey (FIDO2) authentication methods policy; Risky Agents; Microsoft Entra Agent Registry roles.
The Microsoft single sign-on for Linux is supported with the following operating systems (physical or Hyper-V machine with x86/64 CPUs):
> | Role | Description | Template ID |
- **microsoft-user-default-recommended:** Permissions consentable based on Microsoft's current recommendations.
A Microsoft Entra documentation page was updated: Agent Contact App Owners.
Starting October to November 2027, Microsoft will retire the isAttestationEnforced and keyRestrictions properties from the fido2AuthenticationMethodConfiguration API. These will sync with new properties in the updated passkey policy API schema during transition. Admins must update configurations, automations, and integrations accordingly.
> [!NOTE]
A Microsoft Entra documentation page was updated: Agent App Lifecycle Discovery Onboard.
A Microsoft Entra documentation page was updated: Agent App Lifecycle Management.
For more information about Kerberos in Windows, see [Kerberos authentication overview in Windows Server](/windows-server/security/kerberos/kerberos-authentication-overview).
- [How to use Microsoft Entra health monitoring signals and alerts](/entra/identity/monitoring-health/howto-use-health-scenario-alerts)
A Microsoft Entra documentation page was updated: Agent App Lifecycle Remediation Plans.
In the Microsoft Entra Agent Registry, you can assign roles to administrators or other security principals to manage agent instances, agent card manifests, and agent collections. These roles provide the permissions required to perform specific actions, such as creating or updating agent instances, create agent card manifests, or managing collection membership.
- Using real-time signals such as agent identities risk controlling agent access to resources, with Microsoft Managed Policies providing a secure baseline by blocking high-risk agents.
A Microsoft Entra documentation page was updated: Agent Identify Prioritize Risky Apps.
The following known issues and gaps relate to consent and permissions.
The type of permissions you request depends on how your agent operates and what resources it needs to access.
Learn about the Microsoft Entra Agent ID sign-in process, including consent pages, trust criteria, and how to manage agent permissions for secure access to AI agents using work accounts.
Learn the channels and roles involved in creating Microsoft Entra agent identity blueprints, agent identities, and agent users. Monitor and control their introduction into your tenant.
Agent identities are enabled by default in all Microsoft Entra ID tenants. Customers who want to control which Agent IDs are allowed in their tenant can follow the guidance in this article to configure their preferred settings. Microsoft Entra Agent ID is subject to its [standard preview terms and conditions](/entra/fundamentals/licensing-preview-info).
Learn about currently known issues and errors encountered when using the Microsoft Entra Agent ID preview.
- ID Protection for agents is included with the Microsoft Entra P2 license while in preview.
- [Configure risk policies](../id-protection/howto-identity-protection-configure-risk-policies.md) (Updated)
:::image type="content" source="media/custom-data-resource-access-reviews/upload-access-data-files.png" alt-text="Screenshot of uploading files to custom access data.":::
- Select the **Internet applications blocked by Entra Internet Access Policy** scenario.
- The enforcement feature supports only the baseline profile. Network security policies apply per tenant.
