azureblog.co.uk
← SC-300 study plan
SC-300 · Plan and implement workload identities

Plan and implement app registrations

When to register an app, creating registrations, authentication settings, delegated and application API permissions, and app roles.

  • 15 min
  • 5 concepts
  • Try it yourself
  • 4-question check

Learn

An app registration is the global definition of an app you build: its ID, how it signs in and what it's allowed to call. When it's used in a tenant, a service principal (the enterprise app) is created there from it.

  1. 1

    Plan for app registrations

    Decide the supported account types: this tenant only (single tenant), any Entra tenant (multitenant), or also personal Microsoft accounts. Decide who can register apps (turn off for ordinary users and use Application Developer), the platform (web, single-page app, mobile/desktop), and the credential type: certificates or federated credentials rather than secrets.

    Remember: One registration (global) → a service principal per tenant.

  2. 2

    Create app registrations

    Register in the admin center, CLI (az ad app create) or Graph. Note the Application (client) ID and Directory (tenant) ID. Add owners so management isn't left to admins.

    Remember: Client ID identifies the app; tenant ID identifies the directory.

  3. 3

    Configure app authentication

    Add a platform and its redirect URIs (where tokens are sent after sign-in). Use certificates (preferred) or client secrets (with an expiry, up to 24 months in the portal) for confidential clients, or federated credentials. Configure optional claims and the front-channel logout URL. Turn off implicit grant unless a legacy SPA needs it.

    Remember: Wrong redirect URI = AADSTS50011.

  4. 4

    Configure API permissions

    Delegated permissions let the app act as the signed-in user, limited to what the user can do. Application permissions let the app act as itself with no user, such as a background service, and always need admin consent. Request least privilege, for example User.Read rather than User.Read.All.

    Remember: No user present? Application permissions plus admin consent.

  5. 5

    Create app roles

    Define app roles in the registration (display name, value, allowed member types: users/groups, applications or both). Assign users and groups to them in the enterprise app, or grant them to other apps as application permissions. The app checks the roles claim in the token to authorise actions.

    Remember: App roles = authorisation inside your own app.

Delegated or application permission?

Delegated
  • A user is signed in
  • App acts on the user's behalf
  • Limited by the user's own access
  • User or admin consent
Application
  • No signed-in user
  • App acts as itself
  • Access across the tenant
  • Always admin consent

Try it

Which setting or concept is it?

This interactive part needs JavaScript.

In the portal

  • New registrationEntra admin center: Entra ID > App registrations > New registration
  • API permissionsEntra admin center: Entra ID > App registrations > your app > API permissions
  • App rolesEntra admin center: Entra ID > App registrations > your app > App roles

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your SC-300 study plan.

  1. Which permission type always needs admin consent?

  2. What's created in each tenant that uses your app?

  3. Which credential type is preferred over client secrets?

  4. Where does an app read the user's assigned app roles?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.