Azure App

  • Which Type of Azure Application Do You Wish to Onboard? – Select the type of application you wish to integrate with Azure. Types include:

    • Non-gallery Enterprise Applications (SAML)

    • Gallery Enterprise Applications (SAML)

    • Application Registration (OIDC)

  • In Which Environment Will It Be Deployed? – Select the appropriate environment for the application. Depending on the value of the AzureAppApplicationLine list data set, the choices displayed may differ from those below. The option selected has no effect on where the application is created; it is metadata that EmpowerID stores in an extension attribute on the application.

 

  • Select a Tenant – Search for and select the Azure tenant in which the application is to be created.

  • Select a Location – Select a location in EmpowerID for the application. This location is for RBAC delegation only.
    If there is a location selected by default and you wish to change it, click the link for the location and then search for and select the desired location from the Location tree.

 

  • Azure Application Name – Enter a name for the application

  • Azure Description – Enter a description for the application

 

Select the scope for selecting which accounts can use the application. Default options include the following:

  • Personal Microsoft accounts only

  • Accounts in this organizational directory only (Single tenant)

  • Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g., Skype, Xbox)

  • Accounts in any organizational directory (Any Azure AD directory - Multitenant)

 

  • Application Owner – Search for and select the application owner. This field only returns people with an account in the Azure tenant.

  • Select Deputies – Search for and select one or more application deputies. This field only returns people with an account in the Azure tenant.

 

  • Select A Platform – Select a platform the application is targeting. Options include:

    • Web – Build, host, and deploy web server applications

    • Single-page application – Configure browser client applications and progressive web applications

    • Mobile and desktop applications – iOS/macOS, Android applications

  • Front-Channel Logout URL – Enter URL as needed

  • Issue Access token (used for implicit flows) – Select as needed

  • Issue ID tokens (used for implicit and hybrid flows) – Select as needed

  • Allow Public Client Flows – Specifies whether the application is a public client. Appropriate for apps using token grant flows that don’t use a redirect URI.

  • User Access Settings

    • Enabled for users to sign-in? – Enabled by default

    • Assignment required? – Enabled by default

 

  • Set Requestable Setting – Specifies whether the application is requestable in the IAM Shop. When selected, the below settings are relevant.

  • Select Access Request Policy – Select the Access Request policy that specifies how requests for the application are processed.

  • Select Assignees – Search for and select users who are eligible for the application. Users must have one of the below eligibility assignments to view the application in the IAM Shop.

    • Eligible Assignees – Choose the type (Person, Group, SetGroup, Management Role, Business Role and Location), and then search for and select the specific assignees eligible for the application.

    • Preapproved Assignees – Choose the type (Person, Group, SetGroup, Management Role, Business Role and Location), and then search for and select the specific assignees pre-approved for the application.

    • Suggested Assignees – Choose the type (Person, Group, SetGroup, Management Role, Business Role and Location), and then search for and select the specific assignees suggested for the application.