Microsoft Entra admin center
UpdatedOverview of the Microsoft Entra admin center interface for configuring and managing Microsoft Entra products.
Day in brief
Agent ID architecture guidance expanded on 4 April; no service rollout is evidenced
The day's most substantive work focused on Microsoft Entra Agent ID: two new architecture pages were added, while related identity, service-principal, and design-pattern guidance was revised. The evidence describes Microsoft Learn documentation changes, not a feature launch, preview, general availability announcement, retirement, or changed tenant behavior. The remaining notable entries are updates to existing External ID and Entra ID administration guidance.
- New Microsoft Entra Agent ID design-patterns guidance
Agent ID · ArchitectureMicrosoft Learn added a new article that maps AI-agent architectures to blueprints, agent identities, and an agent's user account. This is new architecture documentation, not evidence of a product launch or availability change.
- New decision guide for planning Agent ID architectureAgent ID · Architecture
A new guide helps teams choose the identity type, operation pattern, and blueprint and agent-identity structure for AI agents. It provides an architecture-planning aid; the record does not announce preview, general availability, or a tenant behavior change.
- Agent service-principal guidance was updated
Agent ID · AuthenticationUpdated guidance explains how agent service principals differ from traditional service principals in authentication, permissions, and lifecycle management. The change improves coverage of the Agent ID identity model, but does not state that permission or lifecycle behavior changed in the service.
- External ID planning guidance highlights token-claim requirements
External ID · FundamentalsThe updated Planning Your Solution page notes that applications requiring specific user attributes can include them in the token sent to the application. The supplied evidence supports a documentation clarification, not a change to token issuance or supported claims.
- Joined-device local-administrator guidance was updated
Entra ID · GeneralThe updated Entra ID guide covers assigning Azure roles to the local administrators group of a Windows device. It documents an administration approach but does not identify a new role or changed device behavior.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
14 updates
Microsoft Entra ID
3 updatesLearn how to assign Azure roles to the local administrators group of a Windows device.
ai-usage: ai-assisted
Microsoft Entra Agent ID
6 updatesLearn how to map your AI agent architecture to Microsoft Entra Agent ID, including blueprints, agent identities, and an agent's user account.
Use this decision guide to choose the right identity type, operation pattern, and blueprint and agent identity structure for your AI agents in Microsoft Entra Agent ID.
Agent Id Design Patterns
UpdatedThis article describes common AI agent deployment patterns and how they map to Microsoft Entra Agent ID. The article starts with a review of key identity concepts, describes permisssions and trust boundaries, and then walks through common deployment patterns.
1. **How many blueprints** your system requires.
Learn about agent service principals in Microsoft Entra and how they differ from traditional service principals in authentication, permissions, and lifecycle management.
Discover the role of agent identities in AI authentication. Understand their unique identifiers, token usage, and how they enable secure access to systems.
Microsoft Entra ID Governance
1 updateLifecycle Workflow Templates
UpdatedConceptual article discussing workflow templates and categories with Lifecycle Workflows.
Microsoft Entra External ID
4 updatesai-usage: ai-assisted
Customers Ciam
UpdatedYou can create a simple sign-up and sign-in experience for your customers by adding a user flow to your application. The user flow defines the series of sign-up steps customers follow and the sign-in methods they can use (such as email and password, one-time passcodes, social accounts from [Google](how-to-google-federation-customers.md), [Facebook](how-to-facebook-federation-customers.md), or [Apple](how-to-apple-federation-customers.md), [Microsoft Entra ID](how-to-entra-id-federation-customers.md) federation, as well as [custom OIDC](how-to-custom-oidc-federation-customers.md) identity providers). You can also collect information from customers during sign-up by selecting from a series of user built-in attributes or adding your own custom attributes.
Planning Your Solution
Updated- **Requirements for token claims**. If your application requires specific user attributes, you can include them in the token sent to your application.
Supported Features Customers
UpdatedCompare features and capabilities of a workforce versus an external tenant configuration. Determine which tenant type applies to your external identities scenario.