# Initial app registration in Microsoft Azure

For ELO Azure Administration to connect to Microsoft Azure, you will have to register the app in Microsoft Azure first.

Please note

This documentation does not cover basic configuration of a Microsoft Azure environment or subscriptions, both of which are required for this.

  1. Log on to Microsoft Azure as an administrator.

    'Microsoft Entra ID' area; 'App registrations' menu item

  2. Go to App registrations.

    'App registrations' area; 'New registration' button

  3. Select New registration.

    The Register an application page opens.

  4. Enter a name for the app. You can choose any name you like.

    Example: ELO Azure Administration

  5. Under Supported account types, select Accounts in any organizational directory and personal Microsoft accounts (any Microsoft Entra ID tenant – multi-tenant capable) and personal Microsoft accounts (e.g. Skype, Xbox).

  6. Select Register.

    The app is registered in Microsoft Azure.

# Authentication settings

Once registration is complete, you have to configure some settings for app authentication.

  1. In Microsoft Azure, go to Authentication.

    'Authentication' button

  2. Select Add a platform.

    The Configure platform area appears.

  3. Select Single-page application.

    Top section of the 'Configure single-page application' area

    The Configure single-page application area opens.

  4. In the Enter the redirect URI field, enter a URL as follows:

    https://<Server>:<Port>/ix-<Repository>/plugin/de.elo.ix.plugin.proxy/azadministrations/auth-end/blank.html

    Example:

    https://desktop-8luhtiv:9093/ix-EXTEN/plugin/de.elo.ix.plugin.proxy/azadministrations/auth-end/blank.html

    Information

    The URL must match the path to ELO Azure Administration in the respective ELO environment.

  5. Enable the following settings:

    • Access tokens (used for implicit flows)
    • ID tokens (used for implicit and hybrid flows)
  6. Save the settings with Configure.

    The authentication settings are now configured.

# API permissions

The app for ELO Azure Administration requires several permissions.

'API permissions' button

  1. Open the API permissions area.

  2. Select Add permissions.

    The Request API permissions area opens.

  3. Add the following delegated permissions:

    • Azure Service Management:
      • user_impersonation
    • Microsoft Graph:
      • Application.ReadWrite.All
      • Directory.ReadWrite.All
      • RoleManagement.ReadWrite.Directory
      • User.Read
      • User.ReadWrite.All

'Configured permissions' area; button for granting admin consent

  1. Select Grant admin consent for <tenant>.

    The Confirm admin consent dialog box opens.

  2. Click Yes to confirm.

    The permissions are added.

# Configuring the service

Once the app has been set up in Azure, you now have to update the configuration of ELO Azure Administration in the ELO system.

  1. In Microsoft Azure, open the overview for the app you created above.

    Azure app overview, with the 'Display name' and 'Application ID (client)' fields selected

  2. Copy the values of the following fields:

    • Display name
    • Application ID (client)
  3. On the server machine running ELO, open the following directory:

    <ELO>\servers\ELO-Azure-Administration

    Information

    The placeholder <ELO> stands for the ELO installation directory.

  4. Open the appsettings.json file in a suitable editor.

    You will find the following entries in the header area of the file:

      "AppsManagementDashboard": {
        "MicrosoftAppId": "",
        "MicrosoftAppName": ""
      },   
    
  5. Insert the copied values into the JSON file.

    Example:

      "AppsManagementDashboard": {
        "MicrosoftAppId": "cc810f16-0766-49d9-a6b6-b1c8e3286cb4",
        "MicrosoftAppName": "ELO Azure Administration"
      },
    
  6. Save the file.

  7. Restart the ELO Azure Administration service.

    Service configuration is now complete. You can now authenticate with Microsoft Azure via ELO Azure Administration.

Last updated: June 18, 2024 at 11:27 AM