Since November 4, 2026, users without a Microsoft Entra role can create agent blueprints by default, unless the administrator decides otherwise. This change calls for two immediate checks: inventory the existing resources and verify the policy actually applied to the tenant.
Why this check is now a priority
The rollout announced in MC1506733 changes the default behavior of Microsoft Entra Agent ID. When it reaches a tenant, the blueprint creation setting may be set to “Yes”, including in a test environment that has never been explicitly configured.
May 1, 2026
Agent 365 becomes available
Microsoft announces the general availability of Agent 365 for the Commercial segment. The service is included in Microsoft 365 E7 or offered separately at USD 15 per user per month.
November 4, 2026
Start of the default value change
Standard users can create agent blueprints if the administrator has not disabled the setting.
End of November 2026
Announced end of the rollout
A preference saved before the change arrives should take effect when the rollout reaches the tenant.
The issue goes beyond simply creating an Entra object. A blueprint without a clearly identified owner, or an associated principal whose responsible team is no longer known, becomes hard to fit into access review and lifecycle management processes. This issue complements centralized agent governance with Agent 365.
In a test tenant that already shows “Yes”, the right sequence is to export a baseline, identify objects without an owner, then explicitly save the expected value. This method avoids confusing the absence of resources, the absence of visibility, and effective governance.
What the setting actually blocks
The setting is named Users can create agent blueprints in the Message Center and in the documentation. According to Jan Bakker’s analysis, the portal may however display Users can register agent identity blueprints, under “Users can register applications”.
This difference in wording does not change the corresponding Graph property: defaultUserRolePermissions.allowedToCreateAgentIdentityBlueprints in authorizationPolicy. It does mean you should check the text displayed in each tenant before producing an internal procedure or screenshots.
The value false removes the creation right from standard users. It is not a universal denial:
- it is independent of Users can register applications;
- the Agent ID Developer and Agent ID Administrator roles retain the ability to create blueprints;
- an application with a permission such as
AgentIdentityBlueprint.Createcan use its own authorization path; - the owner of a blueprint can create agent identities from it;
- existing blueprints are neither disabled nor deleted.
Disabling is not retroactive
Setting the parameter to “No” reduces future creations by standard users. Inventorying and remediating existing objects remain separate operations.
The sponsor must not be confused with the owner. The sponsor is required at creation, while the owners relationship is optional. An object without an owner is therefore not necessarily incomplete from the API’s point of view, but it deserves a governance review.
Prerequisites, permissions and Graph endpoints
The script relies only on the Microsoft.Graph.Authentication module and on Invoke-MgGraphRequest. It thus avoids depending on dedicated cmdlets whose availability could differ between SDK versions.
1Install-Module Microsoft.Graph.Authentication -Scope CurrentUser2Get-InstalledModule Microsoft.Graph.Authentication | Select-Object Name, Version| Operation | Graph endpoint | Minimum delegated permission |
|---|---|---|
| List blueprints, principals and their owners | v1.0 — servicePrincipals and owners relationship | Application.Read.All |
| Read the creation setting | beta — policies/authorizationPolicy | Policy.Read.All |
| Modify the creation setting | beta — policies/authorizationPolicy | Policy.ReadWrite.Authorization |
The agentIdentityBlueprint and agentIdentityBlueprintPrincipal resources are available in Microsoft Graph v1.0. The policy property, however, is still exposed by /beta/policies/authorizationPolicy. Both versions must therefore be used deliberately, without switching the whole script to beta.
The documentation on creation channels also states that a blueprint created through Graph, PowerShell or CLI does not automatically get a principal: it must be created manually. To consent to Graph application permissions during creation, the Privileged Role Administrator role is required in addition to the appropriate Agent ID role.
No fixed propagation delay after a PATCH is provided in the documented material. Reading back through Graph immediately confirms the stored value; during the gradual rollout of November 2026, its functional effect may have to wait until the change reaches the tenant.
Implementation: producing the Agent ID inventory
The following script queries the typed collections Microsoft.Graph.AgentIdentityBlueprint and Microsoft.Graph.AgentIdentityBlueprintPrincipal in v1.0. For each object, it retrieves the /owners relationship, counts the owners and generates a directly usable CSV file.
Prerequisites: Microsoft.Graph.Authentication module. Permission: Application.Read.All. Output: a PowerShell table and a CSV containing the type, name, identifiers, owner count and their description.
1#Requires -Modules Microsoft.Graph.Authentication2 3[CmdletBinding()]4param(5 [Parameter()]6 [string]$OutputPath = (Join-Path -Path $PWD -ChildPath ("entra-agent-id-inventory-{0}.csv" -f (Get-Date -Format "yyyyMMdd-HHmmss")))7)8 9$ErrorActionPreference = "Stop"10Import-Module Microsoft.Graph.Authentication11 12# L’inventaire des service principals et de leurs propriétaires requiert Application.Read.All.13Connect-MgGraph -Scopes @("Application.Read.All") -NoWelcome14 15function Get-GraphCollection {16 [CmdletBinding()]17 param(18 [Parameter(Mandatory)]19 [string]$Uri20 )21 22 $results = [System.Collections.Generic.List[object]]::new()23 24 do {25 $page = Invoke-MgGraphRequest -Method GET -Uri $Uri -OutputType PSObject26 27 foreach ($item in @($page.value)) {28 [void]$results.Add($item)29 }30 31 $Uri = $page.'@odata.nextLink'32 }33 while (-not [string]::IsNullOrWhiteSpace($Uri))34 35 return $results36}37 38$resourceDefinitions = @(39 [pscustomobject]@{40 ResourceType = "agentIdentityBlueprint"41 Uri = "https://graph.microsoft.com/v1.0/servicePrincipals/Microsoft.Graph.AgentIdentityBlueprint"42 },43 [pscustomobject]@{44 ResourceType = "agentIdentityBlueprintPrincipal"45 Uri = "https://graph.microsoft.com/v1.0/servicePrincipals/Microsoft.Graph.AgentIdentityBlueprintPrincipal"46 }47)48 49$inventory = foreach ($definition in $resourceDefinitions) {50 $resources = @(Get-GraphCollection -Uri $definition.Uri)51 52 foreach ($resource in $resources) {53 # La relation owners peut contenir plusieurs types d’objets d’annuaire.54 $ownersUri = "https://graph.microsoft.com/v1.0/servicePrincipals/$($resource.id)/owners"55 $owners = @(Get-GraphCollection -Uri $ownersUri)56 57 $ownerLabels = foreach ($owner in $owners) {58 $ownerName = if ([string]::IsNullOrWhiteSpace([string]$owner.displayName)) {59 "Nom non exposé"60 }61 else {62 [string]$owner.displayName63 }64 65 "{0} <{1}> [{2}]" -f $ownerName, $owner.id, $owner.'@odata.type'66 }67 68 [pscustomobject]@{69 ResourceType = $definition.ResourceType70 DisplayName = $resource.displayName71 ObjectId = $resource.id72 AppId = $resource.appId73 OwnerCount = $owners.Count74 IsOrphaned = ($owners.Count -eq 0)75 Owners = ($ownerLabels -join " | ")76 }77 }78}79 80$inventory |81 Sort-Object ResourceType, DisplayName |82 Export-Csv -Path $OutputPath -NoTypeInformation -Encoding utf883 84$inventory |85 Sort-Object ResourceType, DisplayName |86 Format-Table ResourceType, DisplayName, ObjectId, OwnerCount, IsOrphaned -AutoSize87 88Write-Host "Inventaire exporté vers : $OutputPath"89Disconnect-MgGraph | Out-NullMicrosoft Graph also supports $filter on the owner count for principals. The script deliberately retrieves each relationship: it must return the names and identifiers of the owners, not just detect orphaned objects. This approach complements the first Agent 365 APIs available in Microsoft Graph.
To analyze the CSV without modifying the tenant, use this second script:
1[CmdletBinding()]2param(3 [Parameter(Mandatory)]4 [ValidateScript({ Test-Path -Path $_ -PathType Leaf })]5 [string]$CsvPath6)7 8$inventory = Import-Csv -Path $CsvPath9 10Write-Host "Répartition par type de ressource :"11$inventory |12 Group-Object ResourceType |13 Select-Object Name, Count |14 Format-Table -AutoSize15 16Write-Host "Ressources sans propriétaire :"17$inventory |18 Where-Object { [int]$_.OwnerCount -eq 0 } |19 Select-Object ResourceType, DisplayName, ObjectId, AppId |20 Format-Table -AutoSizeChecking, then changing the creation right
Tenant-wide change
The property belongs to the global authorization policy. Run the script with -WhatIf first, keep the initial value, and have the change approved by the identity governance lead.
Open the user settings
In the Microsoft Entra admin center, open Identity > Users > User settings.
Identify the label present in the tenant
Look for Users can create agent blueprints or Users can register agent identity blueprints, under the setting related to application registration.
Explicitly save the value
Select “No” to prevent standard users from creating new blueprints, then save. This action does not delete any existing resource.
The After value must be False. This output confirms the value was saved in Microsoft Graph, but on its own it does not confirm that the MC1506733 change has arrived in a tenant that is still being rolled out.
Verifying the result and resolving discrepancies
After the write, reload the portal page and read /beta/policies/authorizationPolicy again in a new Graph session. For existing resources, compare the CSV with the list of responsible teams and handle blueprints and principals without an owner separately.
| Symptom | Probable cause | Resolution |
|---|---|---|
| The property does not appear in the response | Request sent to v1.0 or token without Policy.Read.All | Use the beta endpoint and reconnect Microsoft Graph with the required permission |
| The portal still shows “Yes” after the script | Cached page, wrong label checked, or MC1506733 rollout not finished | Read the value through Graph again, refresh the portal and check the tenant rollout status |
| Users still create blueprints | Agent ID role or application with a dedicated Graph permission | Audit role assignments and authorized applications instead of changing only the default policy |
| Existing blueprints remain visible | The setting is not retroactive | Keep, reassign or handle the existing resources in a separate governance effort |
| A blueprint created by automation has no principal | Graph, PowerShell and CLI do not automatically create this principal | Create the principal manually following the channel documented by Microsoft Learn |
| OwnerCount is zero despite the presence of a sponsor | The sponsor and the owners relationship are distinct | Assign an owner if the organization’s governance model requires it |
For a functional check, use a test account with no Entra role and no intermediary application holding AgentIdentityBlueprint.Create. This test is essential: a privileged account cannot validate the behavior intended for standard users.
Frequently asked questions
Does disabling the setting delete existing blueprints?
No. The value false prevents certain future creations, but it neither deletes nor disables blueprints that are already registered. Their inventory, assignment and possible removal must be managed separately.
Is disabling “Users can register applications” enough?
No. The two settings are independent. You must explicitly control allowedToCreateAgentIdentityBlueprints to govern the creation of agent blueprints by standard users.
Can you use Microsoft Graph v1.0 only?
Not for the whole procedure. Blueprints, principals and their owners are accessible in v1.0, but the allowedToCreateAgentIdentityBlueprints property of the authorization policy is still read and modified via beta.
Why can a user still create a blueprint after the block?
The setting does not apply to the same authorization paths as the Agent ID roles or Graph application permissions. Check the Agent ID Developer and Agent ID Administrator roles and the applications holding a creation permission.
Where to start
The recommended strategy is to block creation by default if the organization does not yet have an explicit approval process, then delegate the necessary creations through controlled roles and applications.
Checks before going to production
- Export the inventory of blueprints and principals
- Keep the initial value of
allowedToCreateAgentIdentityBlueprints - Review all resources whose
OwnerCountis zero - Check the Agent ID roles and authorized applications
- Run the change with
-WhatIf - Confirm that the Graph read-back returns
False - Check the label and value in the Microsoft Entra portal
- Test with a user who has no Entra role
If your organization allows self-service creation, do not simply leave the default value active: document the expected owners, the sponsor’s role, the review frequency and the removal process. The joint governance of Agent 365 and Microsoft Entra Agent ID provides the complementary framework for this decision.
Going further
- Create an agent identity blueprint — the roles, prerequisites and effects of the creation setting.
- Prevent users from creating new agent identity blueprints — the Graph control of the property and the paths that bypass the block.
- Microsoft Entra Agent ID APIs in Microsoft Graph — the API’s resources, owners, sponsors and permissions.
- Microsoft Plans to Allow Users to Create Agent Blueprints — the analysis of the default value change.
- MC1506733 – Review who can create agents in Microsoft Entra — the schedule, scope and limits of the rollout.



