Daily.Entra.News32 changes were tracked across 3 Microsoft Entra products. The leading updates include Acquire a token to call a web API using username and password (desktop app); Microsoft Entra: New service plans for Conditional Access and ID Protection for agents; Migrate Copilot Studio Agents To Agent Id.
author: Dickson-Mwendia
author: Dickson-Mwendia
| `jobTitle` |Any string value or `null` | ```user.jobTitle -eq "value"``` |
ai-usage: ai-assisted
- Each dynamic group can have up to 50 member groups.
- Read AI-related enterprise services, extensibility, and copilot agents
Learn how to configure daemon apps that call web APIs using secrets, certificates, or client assertions.
Learn how autonomous agents acquire tokens using the Microsoft Entra ID Auth SDK (sidecar) to call downstream APIs independently.
This article shows the new and updated documentation for the Microsoft Entra application management.
> [!NOTE]
ai-usage: ai-assisted
Understand how the username and password (ROPC) flow works in desktop apps, why it is deprecated, and how to migrate to more secure authentication flows.
**Has filter** indicates whether the policy has app filters that use custom security attributes.
- [Microsoft Entra ID Auth SDK (sidecar) documentation](/entra/msidweb/agent-id-sdk/overview)
Traditional service principals were designed for static, deterministic workloads. Microsoft Entra Agent ID exists because service principals lack the governance infrastructure AI agents need. There's no enforced sponsorship, no agent-aware audit entries, and no blueprint-managed lifecycle. For more information, see [Agent identities, service principals, and applications](agent-service-principals.md).
To call an API from an agent, you need to obtain an access token that the agent can use to authenticate itself to the API. We recommend using the *Microsoft.Identity.Web* SDK for .NET to call your web APIs. This SDK simplifies the process of acquiring and validating tokens. For other languages, use the [Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/overview).
- [Call API: Azure services](../agent-id/call-api-azure-services.md) (New)
author: Dickson-Mwendia
author: Dickson-Mwendia
Deploy n8n on Azure Container Apps and secure AI agent workflows with Microsoft Entra Agent ID and Microsoft Graph MCP Server for Enterprise.
> [!WARNING]
author: Dickson-Mwendia
author: Dickson-Mwendia
- **Authentication service**: An OAuth 2.0 and OpenID Connect (OIDC) standard-compliant authentication service that enables secure, standards-based authentication for agents. This service issues tokens that agents use to authenticate to resources and APIs, supporting both application-only and delegated access scenarios. There are three objects that form the core identity constructs in the platform: agent identity blueprint, agent identity, and agent's user account.
Microsoft is adding new Entra service plans—Conditional Access for Agents and ID Protection for Agents—to Microsoft Agent 365 and Microsoft 365 E7, enabling secure agent identity management. Rollout starts July 2026, with automatic enabling and no policy changes. No action required, but license review is recommended.
- [Configure Entra ID Auth SDK (sidecar) for agent identities](microsoft-entra-sdk-for-agent-identities.md)
author: Dickson-Mwendia
- [AI-guided setup](agent-id-ai-guided-setup.md) (New) - Automate onboarding with an AI coding agent that walks you through blueprint creation, credential configuration, and agent identity provisioning.
Set-Location -Path "C:\"
1. Select **Download Client**.
Learn how AI agent discovery in Global Secure Access provides network-level visibility into managed and shadow AI agents reaching the internet from your environment.
