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

Integrate and manage enterprise applications

Enterprise app settings, app admin roles, Application Proxy for on-premises apps, SaaS single sign-on, assignment and app roles, user and admin consent, and My Apps collections.

  • 20 min
  • 7 concepts
  • Try it yourself
  • 4-question check

Learn

Every app your users sign in to through Entra ID appears as an enterprise application (a service principal) in your tenant. This is where you set up single sign-on, decide who can use the app, and control what it can access on users' behalf.

  1. 1

    Plan and implement settings for enterprise applications, including application-level and tenant-level settings

    App-level properties: enabled for users to sign in, assignment required (only assigned users and groups get in), visible to users in My Apps, logo and owners. Tenant-level settings: user consent, admin consent workflow, and whether users can add gallery apps to My Apps.

    Remember: Assignment required = yes, unless everyone should get in.

  2. 2

    Assign appropriate Microsoft Entra roles to users to manage enterprise applications

    Application Administrator manages all enterprise apps and app registrations, including Application Proxy. Cloud Application Administrator does the same except Application Proxy. Application Developer can create registrations. App owners can manage just their apps. Neither app admin role can grant consent for Microsoft Graph application permissions; that needs Privileged Role Administrator or Global Administrator.

    Remember: Cloud Application Admin = Application Admin minus App Proxy.

  3. 3

    Design and implement integration for on-premises apps by using Microsoft Entra Application Proxy

    Application Proxy publishes on-premises web apps for remote access without a VPN or opening inbound ports. Install private network connectors (outbound only) on-premises, group them, and publish the app with an external URL. Pre-authentication with Entra ID means Conditional Access applies before traffic reaches the network. SSO options include Kerberos constrained delegation and header-based.

    Remember: No inbound firewall ports: connectors call out.

  4. 4

    Design and implement integration for software as a service (SaaS) apps

    Add SaaS apps from the Entra app gallery or as non-gallery apps. Configure SSO with SAML (identifier, reply URL, signing certificate, claims) or OpenID Connect/OAuth, or password-based SSO for apps without federation. Many gallery apps also support automatic user provisioning with SCIM. Watch SAML signing certificate expiry (three years by default).

    Remember: SAML certificates expire: set notification emails.

  5. 5

    Assign, classify, and manage users, groups, and app roles for enterprise applications

    Assign users and groups (nested groups aren't supported for assignment) to an app, optionally with an app role such as Reader or Approver that the app reads from the token. Assigning groups needs P1. Hide apps users don't need from My Apps, and review assignments with access reviews.

    Remember: App roles appear in the token's roles claim.

  6. 6

    Configure and manage user and admin consent

    When an app asks for permissions, a user or admin must consent. Restrict user consent to apps from verified publishers asking for low-impact permissions, or turn it off. Turn on the admin consent workflow so users can request approval. Admins can grant tenant-wide consent and review and revoke granted permissions on the app's Permissions page.

    Remember: Users request, admins approve: admin consent workflow.

  7. 7

    Create and manage application collections

    Collections group apps into tabs in the My Apps portal (myapps.microsoft.com), such as HR apps or Finance apps, and can be assigned to specific users or groups. Users can also create personal collections.

    Remember: Collections organise My Apps.

Publishing an on-premises app with Application Proxy

  1. Install connectorsOutbound only, on servers near the app.
  2. Publish the appInternal URL, external URL, pre-authentication with Entra ID.
  3. User signs inConditional Access applies at Entra ID.
  4. Traffic flowsThrough the Application Proxy service and connector to the app.

Try it

An app asks for permissions. Your tenant allows user consent only for verified publishers and low-impact permissions, and the admin consent workflow is on.

This interactive part needs JavaScript.

In the portal

  • Enterprise appsEntra admin center: Entra ID > Enterprise apps > All applications
  • Consent settingsEntra admin center: Entra ID > Enterprise apps > Consent and permissions
  • Application ProxyEntra admin center: Global Secure Access > Connect > Connectors
  • CollectionsEntra admin center: Entra ID > Enterprise apps > App launchers

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 role can manage enterprise apps but not Application Proxy?

  2. Remote users need an internal web app without a VPN or inbound ports. What do you use?

  3. Only assigned users should sign in to an app. Which setting?

  4. Users should be able to ask for consent to blocked apps. What do you enable?

Sources

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