Azure AD configuration and technical details

<< Click to Display Table of Contents >>

Navigation:  Welcome to the Bizagi Modeler 3.7 and Modeler Services documentation > Getting started > Joining the Modeler community  > Signing in to Modeler Services > Signing in with a corporate e-mail >

Azure AD configuration and technical details

Overview

To integrate your Enterprise subscription with your corporate Azure AD you need to carry out the configuration steps as described in this section.

Note that these are done only once, typically by an admin user of your Enterprise plan  having access to your Azure AD.

 

What you need to do

An outline describing the configuration needed to sign in with Azure AD considers these steps:

 

1. Register an authorized application to be used solely by Modeler Services.

2. Communicate to Bizagi for next steps.

 

Configuration

Follow the steps presented to integrate your Azure AD:

 

1. Register an authorized application.

This step is done directly at your Azure portal by doing:

 

1.1 Sign in to Azure's portal at https://portal.azure.com.

 

AzureAD_portal01_1

 

1.2. Go into your Active Directory.

Click on Azure Active Directory option at the left panel to add a new application to it.

 

AzureAD_portal01_2

 

1.3. Add a new app.

Click the App registrations option and click on New registration located in the ribbon.

 

AzureAD_portal03

 

1.4. Input the app's basic details:

 

Give this application a name (can be changed later), select a Supported account Type (Single tenant Recommended) and set

https://accounts-[your_company].bizagi.com

as Redirect URI. Web option must be selected

 

AzureAD_portal04

 

Click Register. The application might take several minutes to create your new application

 

AzureAD_portal05

 

1.5 Make sure that the Redirect URI in the newly created app is ok, to do this, click the Redirect URI option of the newly added app.

 

AzureAD_portal06

 

Make sure is the accounts URL:

 

AzureAD_portal07

 

Open the Expose API menu,  click on Set Application ID URI

 

AzureAD_portal13

 

and configure

https://accounts-[your_company].bizagi.com

as your App ID URI

 

AzureAD_portal08

 

Click Save when done.

 

Add a new Scope and register the following information:

Scope name: https://accounts-[your_company].bizagi.com

Who can consent: Admins and users

 

AzureAD_portal14

 

Add the scope.

 

AzureAD_portal15

 

1.6 Set the Home page URL of the newly created app

To do this, go into the Branding option of the newly added app and set the Home page URL with https://accounts-[your_company].bizagi.com and click Save.

 

AzureAD_portal09

 

1.7 Set the appropriate permissions

To do this, go into the API permissions option of the newly added app and then, click Add a permission.

 

AzureAD_portal10

 

Scroll Down until Supported legacy API and select Azure Active Directory Graph.

 

AzureAD_portal11

 

Select Delegated permissions and set it as is showed in the image:

 

AzureAD_portal12

 

Click Add permissions to finish.

 

 

1.8 Open the Endpoints section of your application:

 

AzureAD_portal16

 

And copy the Federation metadata document:

 

AzureAD_portal17

 

This information needs to be delivered to our support team.

 

2. Communicate with Bizagi for next steps

This step is done by contacting our support team or onboarding manager to share certain information so that the integration is successful.

Communicate to Bizagi the URL of Azure's metadata file employed for this integration.

Note that this URL needs to be publicly-available so that the Bizagi service from the cloud can target it (this file doesn't hold sensitive information).