Azure AD创建Native应用后未显示在应用注册的原因排查

Hey there, let's unpack exactly why this is happening and how to fix it—this is a common gotcha with Azure AD's two separate but linked app management surfaces:

Key Reasons Behind the Behavior #

• Confusion between App Registrations and Enterprise Applications
  Azure AD has two distinct layers for app management:

  • App Registrations: This is where you define your app's identity core—things like reply URLs, client IDs, API permissions, and authentication settings. It's the "template" for your app.
  • Enterprise Applications (service principals): This is the instance of your app within your tenant, used for assigning users/groups, managing access policies, and tracking usage.

  Normally, creating an app from the App Registrations portal automatically generates a matching service principal in Enterprise Applications. But if you created the Native app directly from the Enterprise Applications section (instead of App Registrations), you only get the service principal—no underlying app registration to configure things like reply URLs or add users.

• Outdated Native App Creation Path
  Azure AD has updated its app categories: the old "Native" app option is now grouped under Mobile and desktop applications in the App Registrations portal. If you used a legacy or non-standard entry point to create the app (like an older portal UI or a restricted workflow), it might skip creating the app registration entirely and only spin up the service principal.

• Insufficient Permissions
  If your Azure AD account doesn't have roles like Application Developer or Global Administrator, you might be restricted to only creating/managing Enterprise Applications. Accounts with limited roles (like Cloud Application Administrator) can't create or modify app registrations, so any app you create will only exist in the Enterprise Apps list with limited functionality.

Fixes to Try #

• Recreate the App from the Correct Entry Point
  Head to the App Registrations portal, click New registration, select Mobile and desktop applications as the supported account type, and complete the setup. This will create both the app registration (with all configuration options) and the linked enterprise application.

• Verify Your Account Permissions
  Check with your Azure AD admin to ensure your account has the necessary roles to manage app registrations. The Application Developer role is the minimum needed to create and edit app registrations.

• Link an Existing Enterprise App to an App Registration (Advanced)
  If you need to keep the existing enterprise app, you can manually create a new app registration and associate it with the existing service principal. This requires using Azure PowerShell or the Graph API, though—for most cases, recreating the app is simpler.

内容的提问来源于stack exchange，提问作者Matt Douhan