How to Configure a Non-Gallery Application in Azure with Scale Kit

Learn step-by-step how to create and configure a non-gallery application in Azure using Scale Kit. This guide covers provisioning, user sync groups, and real-time updates.

September 6, 2024 By Jitender Singh Rana

In this guide, we'll learn how to create and configure a non-gallery application in Microsoft Azure. This process is essential for setting up custom applications that are not available in the Azure gallery. By following these steps, you will be able to provision and manage users and groups efficiently, ensuring that your application integrates seamlessly with your existing systems.

Let's get started

To get here from the home page, go to Microsoft Enter ID. Enter ID is Azure's equivalent of Okta. Once there, go to Enterprise Applications. Select "New App." After clicking on it, you will land on a new page where you can create your own application. None of the existing options can be used to configure our scheme because they are specific to the vendors. We will create a non-gallery application. Select the non-gallery option and click on "Create." Name the application "Scale Kit." For Microsoft, it will be "Scale Kit Scheme." This will make sense if someone is reading the guide and needs to create an app via Scale Kit, as it connects to their application through Scale Kit.

Go to Enterprise applications - Microsoft Azure

Step #2: Click on "Home" — Click on "Home"

Step #3: Click on "Microsoft Entra ID" — Click on "Microsoft Entra ID"

Step #4: Click on "Enterprise applications" — Click on "Enterprise applications"

Step #5: Click on "New application" — Click on "New application"

Step #6: Click on "+ Create" — Click on "+ Create"

Step #7: Click on "Create" — Click on "Create"

Step #9: Click on "Create" — Click on "Create"

Type "TestSCIM3"

They are connecting to their application via Scale Kit. Here, you will see a tab labeled "via Scale Kit." Once you have done that, you are inside the app. Now, go to provisioning. First, the app is created. Now, we have to configure it. Last month, it was not done yet; it just created a draft. Now, you have to configure everything. Go to provisioning and select automatic. Provide the tenant URL here. Once this is done, you can save it. After saving, you have another section called mappings enabled. Enable both group and tag. By default, they are enabled, but you can disable them if needed. Specify the operations you want to allow: create, update, delete, or all. I have checked all of them. There is a map created for the username with the user principal name, given name, etc. This is equivalent to the OIDC mapping for SSO. We do not need to change it; we can use it as is. For custom attributes for data sync, we can add new maps later. For groups, it is similar. For now, it is enabled, so we leave it as it is. Close it. Now, since we have done provisioning, we need to enable the provisioning status and turn it on. Save it. Go to user sync groups. Select any existing user or group. Assign the user to this group. Once added, verify in the app, like in Skill Kit DB. When the B2B app is integrated with Skill Kit DB, it sends an event to Skill Kit for provisioning. However, Azure sends updates every 40 minutes, not in real-time. If you want real-time updates, use the provision on demand option. This is not default; by default, it is 40 minutes. Provision on demand allows you to provision whenever you want by clicking on it and specifying which groups or users. This is done manually every time. Normally, when a new employee is added, 40 minutes is acceptable. But if the employee is already in the office and needs immediate access, use provision on demand.