Create Azure Applications

If you have deployed the EmpowerID Azure AD SCIM microservice to Azure and your organization integrates applications with Azure AD, you can manage those applications in EmpowerID to include:

• Creating and deleting applications

• Assigning owners and deputies to applications

• Creating application certificates and secrets

• Creating application roles and scopes

• Assigning users to application roles

• Assign eligibility to applications to specify who can and cannot request access

• Etc.

The workflow used to create Azure applications is the CreateAzureApplication workflow. This workflow has a number of parameters that you can configure to alter the fields that appear when onboarding Azure applications, as well as settings that determine whether human approval is required before EmpowerID fulfills the request and provisions the application in Azure. This article walks through the process for creating an Azure application and demonstrates the following:

• Configuring the parameters of the CreateAzureApplication

• Configuring the roles and ownership EmpowerID assigns to application owners and deputies

• Specifying the approval process (human or automatic)

• Running the workflow

• Verifying the results

Step 1: Configure workflow parameters

The workflow for onboarding Azure applications is CreateAzureApplication. The workflow has several parameters that affect field values. These parameters are listed in the below table. In this example, you set the DefaultAzureTenantID parameter to the Azure tenant where applications are to be created.

Parameter	Description
App_Auth_AssignmentRequired_IsVisible	Boolean value to determine whether the Assignment Required? checkbox is visible.
AppAuth_EnableUserSignIn_IsVisible	Boolean value to determine whether the Enabled for users to sign-in? checkbox is visible.
AppAuth_SupportedAccountType_IsVisible
AppExt_CAP_IsVisible	Boolean value to determine whether the Conditional Access Policy drop down is visible.
AppExt_ExtensionTab_IsVisible	Boolean to determine whether the Application Extension tab of the workflow is visible to users.
AppExt_ExtensionAttribute1_IsVisible	Boolean to determine whether the Application Extension Attribute 1 radio button option is visible. AppExt_ExtensionTab_IsVisible must be set to true for the radio button to be visible.
AppExt_ExtensionAttribute2_IsVisible	Boolean to determine whether the Application Extension Attribute 2 radio button option is visible. AppExt_ExtensionTab_IsVisible must be set to true for the radio button to be visible.
AppExt_ExtensionAttribute3_IsVisible	Boolean to determine whether the Application Extension Attribute 3 radio button option is visible. AppExt_ExtensionTab_IsVisible must be set to true for the radio button to be visible.
AppExt_ExtensionAttribute4_IsVisible	Boolean to determine whether the Application Extension Attribute 4 radio button option is visible. AppExt_ExtensionTab_IsVisible must be set to true for the radio button to be visible.
AppExt_ExtensionAttribute7_IsVisible	Boolean to determine whether the Application Extension Attribute 7 radio button option is visible. AppExt_ExtensionTab_IsVisible must be set to true for the radio button to be visible.
ApplicationLineListDataItemSetName	This specifies the AzureAppApplicationLine list data set of the various application lines that appear to users when selecting the environment for the application. Default list items include those shown below:
ApplicationType_Location_IsVisible	Boolean value that specifies whether the Select a location section of the workflow wizard form is visible to users. Set to true by default.
ApplicationType_Location_SelectaLocation_IsVisible	If ApplicationType_Location_IsVisible is true, this Boolean value determines if the Select a Location tree is visible. Set to true by default.
ApplicationType_Location_Tenant_IsVisible	If ApplicationType_Location_IsVisible is true, this Boolean value determines if the Select a tenant drop-down is visible. Set to true by default.
DefaultAzureRBACManagerAppName	Specifies the default Azure RBAC Manager application used by EmpowerID to manage Azure RBAC resources. Set to EIDAzureRBACManager by default.
DefaultAssignmentRequired	Boolean value on the Azure service principal that determines if users and apps or services must first be assigned the application before accessing it. Set to true by default.
DefaultAzureTenantID	This is the GUID of the Azure tenant. If the value is present, the Select a Tenant drop-down will be auto filled with the specified tenant. You can find the Tenant ID for your Azure tenant by navigating to Azure RBAC Manager > Resources and selecting the Tenants tab.
DefaultEmailMessageID
DefaultEnabledUsersSignIn	Boolean value on the Azure Service Principal that determines if assigned users will be able to sign in to this application, either from My Apps, the User access URL, or by navigating to the application URL directly.
DefaultOrgZoneID	Optional setting that specifies the Org Zone ID of the EmpowerID location that should be populated in the Select a Location tree drop-down.
DefaultSupportedAccountType	Default value that specifies the Microsoft accounts that are supported for the application.
ExtensionAttribute1ListDataItemSetName	Boolean to determine whether the Application Extension Attribute 1 radio button option is visible.
ExtensionAttribute2ListDataItemSetName	This points to the AzureAppExtensionAttribute2Choice list data set for displaying custom radio button options. The selected value is stored in the ExtensionAttribute2 attribute of the Protected Application in EmpowerID.
ExtensionAttribute3ListDataItemSetName	This points to the AzureAppExtensionAttribute3Choice list data set for displaying custom radio button options. The selected value is stored in the ExtensionAttribute3 attribute of the Protected Application in EmpowerID.
ExtensionAttribute4ListDataItemSetName	This points to the AzureAppExtensionAttribute4Choice list data set for displaying custom radio button options. The selected value is stored in the ExtensionAttribute4 attribute of the Protected Application in EmpowerID.
IntegrationTypeListDataItemSetName	This points to the AzureAppTypeOfIntegration list data set of the various Application Integration Types. By default, the list contains OIDC, SAML Gallery & SAML Non-Gallery options.
ListDataItemSetTypeName	Internal field for displaying list data items. Do not change the value.
NonGalleryTemplateID	Specifies the default template for creating non-gallery applications. Do not change the value.
ManagementRoleIDsToNotify	Specifies the ID of the Management Role whose members are to be notified each time an Azure application is created.
SupportedAccTypesOIDCListName	This points to the AzureAppSupportedAccountTypes list data set for displaying supported account type radio button options. Default list items include those shown below:
SupportedAccountTypesTemplateListName

To configure workflow parameters, do the following:

1. On the navbar, expand Object Administration and select Workflows.

2. Select the Workflow tab and search for Create Azure Application.

3. Click the Display Name for the workflow.
   

   

    

4. On the View One page for the workflow, expand the Request Workflow Parameters accordion and search for the DefaultAzureTenantID parameter.
   

   

    

5. Click the edit button for the parameter, enter the appropriate Azure Tenant ID in the Value field and click Save.
   

   

    

6. Configure any other settings as needed.

Step 2: Configure approval

The CreateAzureApplication workflow can be configured to allow the EmpowerID system to automatically provision an application in Azure when submitted by an authorized user or to require approval by one or more people before EmpowerID fulfills the request. The setting that determines whether approval is needed is the Do not generate a business request (no approval) setting. If enabled on the workflow, EmpowerID provisions the application without requiring approval; if deselected, EmpowerID generates a business request to create application an Azure application and routes the request for approval. Once approved, EmpowerID fulfills the request and provisions the application in Azure.

To configure whether approval is needed or not, do the following:

1. Navigate to the View One page for the workflow (as shown in Step 1 above) and click the Edit link to put the workflow in Edit mode.
   

   

2. On the Edit One page, toggle Do not generate a business request (no approval) as needed and save your changes.
   

   

Step 3: Configure owner and deputy roles

Owner and deputy settings for Azure applications created in EmpowerID are determined by the Application Configuration settings of Azure RBAC Manager. These settings are listed in the below table.

To configure custom owner and deputy role settings, do the following:

1. On the navbar, expand Apps and Authentication and select Applications.

2. From the Applications tab, search for RBAC and then click the Display Name link for Azure RBAC Manager.
   

   

   
   This directs you to the View One page for the application. From this page, you can manage the application as needed.
   

   

3. On the View One page, select the App Resources tab and then expand the Application Configuration Settings accordion.

4. Click the Edit button for any setting you need to configure with a custom value.
   

   

5. Save your changes.

Step 4: Run the workflow

1. Navigate to the portal for the Resource Admin app in your environment.

2. In Resource Admin, select Applications and then select the Workflows tab.
   

   

3. Click Onboard Azure Application.
   

   

   
   This opens the Create Azure Application wizard workflow. Follow the wizard and fill in the fields of each section of the workflow with the appropriate information for your application.
   

   

   
   
   

   • 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.

4. Review the summary information for the application and then click Submit.
   
   If you configured the workflow to require approval, you should that a business request for the Azure application was successfully created. The business request must be approved by each designated approver before EmpowerID fulfills the request and creates the application.
   

   

5. Click Submit to exit the wizard.

Step 5: If configured: Approve the Business Request

If the workflow was configured to require approval, do the following to approve the business request; otherwise, move to Step 6 below and verify the application in Azure.

1. Navigate to the portal for the My Tasks application and log in as a user who can approve the request.

2. In My Tasks, locate the Business Request for creating the application and click the Pending button.
   

   

3. Click Run Workflow.
   

   

4. Review the information in the Running Approval Workflow dialog and click Approve.
   

   

   
   You should see the request is completed and pending fulfillment, which occurs when the system creates the application in Azure.
   

   

Step 6: Verify the application in Azure

After the request to create an Azure application has been approved and EmpowerID has fulfilled the request, you should be able to confirm the application has been created in Azure with the owner and deputies specified when the application was created.

1. Log in to your Azure portal and navigate to Azure AD > Enterprise applications.

2. Select All Applications as the Application type and then search for the application you just created.

   You should see the application.

3. Click the Name link for the application to navigate to the Overview blade for the app.

4. Under Manage, click Owners.

   You should seethe Application owner and any deputies you specified for the application when you created it in EmpowerID.