Microsoft quietly expands the Entra Application Developer role

  • Post author:
  • Post category:Microsoft Entra / News
  • Post last modified:
  • Reading time:2 mins read
  • Post published:
Microsoft quietly expands Entra Application Developer

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/update
  • microsoft.directory/applications/audience/update
  • microsoft.directory/applications/authentication/update
  • microsoft.directory/applications/basic/update
  • microsoft.directory/applications/credentials/update
  • microsoft.directory/applications/delete
  • microsoft.directory/applications/disablement/update
  • microsoft.directory/applications/extensionProperties/update
  • microsoft.directory/applications/notes/update
  • microsoft.directory/applications/owners/update
  • microsoft.directory/applications/permissions/update
  • microsoft.directory/applications/policies/update
  • microsoft.directory/applications/tag/update
  • microsoft.directory/applications/verification/update
  • microsoft.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.

Daniel Bradley

Daniel Bradley is a UK-based technical architect and Microsoft MVP in Security. He specialises in Microsoft Entra, Intune, and Microsoft Graph PowerShell and is the author of Microsoft Graph PowerShell for Administrators. He writes and edits Our Cloud Network using experience gained from working with Microsoft cloud environments.

Leave a Reply