Unable to delete Entra app

Question

Unable to delete Entra app

Amit Modi 40 Microsoft Employee

Unable to delete Entra app even though i am the owner of it

VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-06-10T06:56:06.7966667+00:00
Hello Amit Modi,

This issue usually happens due to permission limitations or backend dependencies, even if you are the owner.

Key point: Being an owner of the app is not enough to delete it.

What’s actually causing this

Owner role = can manage app, but cannot delete it

Deletion requires directory-level role (like Application Administrator or Global Administrator)

In some cases, the app may have:

Existing service principal (Enterprise App)

API permissions / assignments

Or it could be a Microsoft/system-created app, which cannot be deleted

What you should do

Confirm your role → Go to Entra ID → Roles and check if you have:

Application Administrator or

Global Administrator

Remove dependencies (if applicable)

Go to Enterprise applications → search the same app → delete service principal

Check and remove:

API permissions

Role assignments

Try deleting again from App registrations

If deletion still fails Try using Graph PowerShell:

PowerShell

Connect-MgGraph -Scopes "Application.ReadWrite.All"

Get-MgApplication -Filter "displayName eq 'AppName'"

Important note

Some applications (especially Microsoft-managed or backend service principals) cannot be deleted by design, and this is expected behavior.

Remove-MgApplication -ApplicationId <AppId>

https://learn.microsoft.com/en-us/entra/identity/users/directory-delete-howto
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-06-11T09:54:43.21+00:00

Amit Modi I’m following up on my previous comment as I haven’t received a response. Please let me know if you need any additional information or assistance from my side.

1 answer

Your answer

VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-06-10T06:56:06.7966667+00:00

Hello Amit Modi,

This issue usually happens due to permission limitations or backend dependencies, even if you are the owner.

Key point: Being an owner of the app is not enough to delete it.

What’s actually causing this

Owner role = can manage app, but cannot delete it

Deletion requires directory-level role (like Application Administrator or Global Administrator)

In some cases, the app may have:

Existing service principal (Enterprise App)

API permissions / assignments

Or it could be a Microsoft/system-created app, which cannot be deleted

What you should do

Confirm your role → Go to Entra ID → Roles and check if you have:

Application Administrator or

Global Administrator

Remove dependencies (if applicable)

Go to Enterprise applications → search the same app → delete service principal

Check and remove:

API permissions

Role assignments

Try deleting again from App registrations

If deletion still fails Try using Graph PowerShell:

PowerShell

Connect-MgGraph -Scopes "Application.ReadWrite.All"

Get-MgApplication -Filter "displayName eq 'AppName'"

Important note

Some applications (especially Microsoft-managed or backend service principals) cannot be deleted by design, and this is expected behavior.

Remove-MgApplication -ApplicationId <AppId>

https://learn.microsoft.com/en-us/entra/identity/users/directory-delete-howto
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-06-11T09:54:43.21+00:00

Amit Modi I’m following up on my previous comment as I haven’t received a response. Please let me know if you need any additional information or assistance from my side.

Answer 1

There are a few common reasons why an Entra application cannot be deleted even if listed as owner.

Check required role and location of the object

For Enterprise applications (service principals), the Delete button is disabled unless the account has one of these roles or is the service principal owner:
- Global Administrator
- Cloud Application Administrator
- Application Administrator
- Owner of the service principal
If the app is a Microsoft application, it cannot be deleted from the UI regardless of role.
If the service principal is for a managed identity, it cannot be deleted from Enterprise applications; it must be managed from the corresponding Azure resource instead.

Delete the enterprise application (service principal) If the app is an enterprise application added to the tenant and the account has the required role:

Using Entra admin center:

Sign in to https://entra.microsoft.com as at least Cloud Application Administrator.
Go to Entra ID → Enterprise apps | All applications.
Search and select the application.
Under Manage, select Properties.
At the top of the Properties pane, select Delete, then confirm.

Using Microsoft Graph PowerShell:

Connect with the right scope:

   Connect-MgGraph -Scopes 'Application.ReadWrite.All'

List service principals and find the one to delete:
```
   Get-MgServicePrincipal
```

Delete it:

   Remove-MgServicePrincipal -ServicePrincipalId 'aaaaaaaa-bbbb-cccc-1111-222222222222'

Using Microsoft Entra PowerShell:

Connect:

   Connect-Entra -Scopes 'Application.ReadWrite.All'

Get and delete by display name:

   Get-EntraServicePrincipal -Filter "displayName eq 'Test-app1'" | Remove-EntraServicePrincipal

Delete the application object (not just the service principal) If the issue is with the application object itself, use Remove-EntraApplication with the ApplicationId:

Remove-EntraApplication -ApplicationId <application-id>

Behavior after deletion

After deletion, the enterprise application stays in the recycle bin for 30 days and can be restored during that period.
After 30 days it is hard-deleted automatically.

If delete is still disabled

Confirm the app is not a Microsoft first‑party app.
Confirm it is not a managed identity service principal.
Confirm the signed-in account has one of the required roles above, not just “owner” of some related resource.
If all conditions are met and the button is still disabled, follow the guidance under Unable to delete an application in the troubleshooting article.

References: