Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.3.5. App Registrations and Enterprise Apps

💡 First Principle: App registrations and enterprise apps represent two sides of the same coin — an app registration defines what an application IS and what it needs (permissions, redirect URIs, secrets), while an enterprise app is the in-tenant instance of that application that gets assigned to users. You need both for an app to work in your organization.

Imagine you're a contractor. Your contractor license (app registration) defines your trade, your bonding, and what you're legally authorized to do. Your badge at a specific job site (enterprise app / service principal) is what actually gets you through the door at that particular location. The license exists once; the badge exists at each site.

ConceptWhat It IsWhere It Lives
App registrationThe definition of the app: its client ID, permissions it needs, secrets, redirect URIsEntra ID → App registrations
Enterprise app (service principal)The in-tenant instance of the app — assigned to users, configured with SSO, has its own permission grantsEntra ID → Enterprise applications
API permissionsWhat data/services the app is allowed to access (e.g., read user profile, send mail)Defined in App registration, granted via consent
ConsentUser or admin approval for the app to access specific permissionsAdmin consent = granted for all users; user consent = per-user

For the exam, the key distinction:

  • You register an app once (or it comes pre-registered for Microsoft's own apps)
  • You configure and assign the enterprise app per tenant
  • Admin consent is required for high-privilege permissions (accessing all user email, reading all files) — users can't grant these themselves
  • Delegated vs application permissions: delegated permissions let the app act on behalf of a signed-in user, and it can reach only what that user can reach; application permissions (app-only access) let the app act as itself with no user present — the model for background services, daemons and unattended agents — and require admin consent because they apply across the tenant
  • Governing consent: every consent grant is recorded in the Entra audit logs, and an enterprise app's Permissions page shows what it has been granted and lets an admin revoke it. Revocation takes effect immediately for everyone using the app. Restricting user consent and turning on the admin consent workflow routes requests for new apps to designated reviewers, so apps are vetted before people come to rely on them

⚠️ Exam Trap: A single app registration can create enterprise apps (service principals) in multiple tenants. Microsoft's own apps — like Teams or SharePoint — are registered by Microsoft but appear as enterprise apps in every customer's tenant. You didn't register Teams; Microsoft did. You configure its enterprise app instance in your tenant.

Reflection Question: A developer builds an internal app that needs to read all users' calendars. They complete the app registration and add the Calendar.Read permission. Users try the app and get permission errors. What step is most likely missing?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned