Microsoft have again quietly expanded another Entra role, this time the Entra Application Developer role with 15 new directory permissions, according to a change recorded on 21 August 2026 by MS Admin Roles. That takes the role from 3 actions to 18, without changing its description or announcing the extra access.
The Microsoft Learn reference still lists only the original permissions to create applications, OAuth 2.0 grants and service principals as owner at the time of writing. The live role definition now also contains:
microsoft.directory/applications/appRoles/updatemicrosoft.directory/applications/audience/updatemicrosoft.directory/applications/authentication/updatemicrosoft.directory/applications/basic/updatemicrosoft.directory/applications/credentials/updatemicrosoft.directory/applications/deletemicrosoft.directory/applications/disablement/updatemicrosoft.directory/applications/extensionProperties/updatemicrosoft.directory/applications/notes/updatemicrosoft.directory/applications/owners/updatemicrosoft.directory/applications/permissions/updatemicrosoft.directory/applications/policies/updatemicrosoft.directory/applications/tag/updatemicrosoft.directory/applications/verification/updatemicrosoft.directory/deletedItems.applications/delete
These are the same application-level actions held by Application Administrator, but the roles are not equivalent. Application Administrator has 73 directory actions, including controls over service principals, consent, App Proxy and application restoration that Application Developer does not have.
The credential permission is the unfortunate addition. We already warn you that an Application Administrator can add a credential to an existing application and authenticate as that workload. If the application already holds a privileged Entra role or high-impact Microsoft Graph application permissions, this creates an attack path beyond the administrator’s own access. Application Developer now appears to inherit that attack path for application registrations, although it cannot grant the privileged Graph consent itself.
Review every active and eligible Application Developer assignment now. Remove assignments that only exist to bypass the tenant’s application-registration setting, and investigate credential, owner and permission changes made to valuable applications after 21 August. A role approved under the old three-action definition should not pass a least-privilege review unchanged.

