Application Manager Only guide · Step 2 of 5

Azure App Registration

For Azure OpenID authentication and Intune connectivity, SoftwareCentral needs a Microsoft Entra ID app registration. The installer can create it automatically — do the manual steps here only if you prefer to prepare it in advance or reuse an existing one.

i Do you need this page?

Shortcut You can skip this page if you will let the installer create the app registration (the Connect to Intune tenant button in Run the installer, section 4). ConfigMgr installations that use Windows Authentication and do not connect to Intune can skip it entirely.

1 Create the registration

  1. In the Azure portal, go to your Entra ID and, in the left menu, click App registrations.
  2. Click the New registration button.
  3. Give the app registration a name.
  4. Choose whether to allow access only for users from this tenant, or from multiple tenants.
  5. Do not enter a Redirect URI yet.
  6. Click Register and proceed.
Entra ID New registration blade with a name entered and account types selected
Entra ID New registration — enter a name, choose the account types, then Register.

2 Copy the IDs

You are taken to the overview page. Here you find the Client ID and Tenant ID that you need in the SoftwareCentral installer.

On the right, there is an Add a Redirect URI button. If you have already created your bindings in the Internet Information Services (IIS) Manager, you can click it and proceed; otherwise continue with the installation of SoftwareCentral and add the redirect URIs later.

App registration overview page with Client ID and Tenant ID
Overview — copy the Client ID and Tenant ID.

3 Add the Web platform

  1. Click the Add a platform button.
  2. Select Web and proceed.
  3. Enter the host name for SoftwareCentral.
  4. Set the front-channel logout URL to the same host name followed by /logout.
  5. Tick the ID tokens checkbox at the bottom.
  6. Click Configure. Do this for both your localhost binding and your regular binding.
Add a platform panel
Click Add a platform.
Web platform configuration with redirect URI, logout URL and ID tokens ticked
Select Web; set the host and /logout URL; tick ID tokens.
Add more redirect URIs later Once you configure a public host name in step 5 of this guide, remember to add it to the app registration's Redirect URIs and to the front-channel logout URL. See Hostname & HTTPS.

4 Best practices

TopicRecommendation
Record the IDsKeep the Client ID and Tenant ID ready for the installer.
Two bindingsAdd the Web platform for both the localhost binding and the regular binding.
New host namesAdd a new host name and the /logout URL when you set up HTTPS (see Hostname & HTTPS).
ConsentGrant admin consent again after every permission change.

5 Troubleshooting

You seeLikely cause and what to do
Sign-in fails with a redirect error on a host nameThe host name is missing from the Redirect URIs. Add it to the Web platform (see Hostname & HTTPS).
Single sign-out does not sign you outThe front-channel logout URL is missing. Add the host name followed by /logout.
The installer cannot create the app registrationThe signed-in account cannot register apps or grant consent. Sign on with an account that can, or create the registration yourself and enter the IDs.
Permissions do not work after you assign themThey may not have taken effect yet, or admin consent was not granted. Wait a few minutes and grant admin consent.
← Previous
1 · Prerequisites