Set up Azure
    • 15 Dec 2024
    • PDF

    Set up Azure

    • PDF

    Article summary

    SysAid’s Azure integration allows you to more efficiently manage the users in your company from one central location, by automatically pulling user data from Azure to SysAid. The integration runs these data imports about every 24 hours; saving time and preventing human error that could occur from manually copying the data. This integration can be configured for multiple Azure tenants.

    While this imports user information from Azure within SysAid, the users themselves cannot access SysAid unless you also enable the Office 365 Single Sign On integration.

    Important:

    If you have users that were imported via LDAP integration, to avoid duplicate users and problems with authentication, make sure that:

    • The users have the same email addresses in the Azure and LDAP repositories

    • The Sync user based on email address check box is selected in the Azure integration settings

    To run these two integrations simultaneously, see Set Up Azure as a Secondary User Repository below.

    Connecting Azure and SysAid

    First, you’ll need to add the Azure addon to your SysAid account:

    1. In SysAid, navigate to Settings >  Integrations > Marketplace.

    2. Select Azure from the addon cards.

    3. Click Get it. You will be redirected to the My apps page where you’ll see Azure.

    4. Click the gear icon.

    Now, you can go ahead and connect the apps - keep your SysAid account in one tab and open a new tab to connect to your Azure portal.

    To connect Azure and SysAid, you’ll need:

    • A Tenant Name

    • A Client ID

    • A Secret Key

    • A Domain Name

    Let’s walk you through where to find the relevant details in Azure.

    Tenant Name:

    1. In the Azure portal, under Azure services, choose Microsoft Entra ID.

    2. In the Overview section, go to Manage > Custom domain names.

    3. Copy the name with an “Available” status and paste it into the Tenant Name field in SysAid.

    Client ID:

    1. Back in Azure, navigate to Azure Active Directory > App Registrations.

    2. Click New Registration.
       IntegrationOffice365NewRegistrationNewRegistration.jpg

    3. In the Name field, enter a name for the application, for example, "SysAid Login".

    4. Click Register.

    5. Back in the app overview screen, click Add a Redirect URI.
       azureSettingsfilesAppRegistration.jpg

    6. Click +Add a Platform.

    7. Click Web.

    8. In the Redirect URL column, add your SysAid account URI.

      Tip:

      Your SysAid URI is the URl that you see when logging into your SysAid account. It should be in the following format:
      https://www.[YourSysAidURI]


       azureSettingsfilesRedirectURLRedirectURL.png

    9. Click Configure.

    10. Click Save.

    11. Click Overview in the menu to the left.

    12. Copy the Application (client) ID for the new SysAid app.
       azureSettingsfilesApplicationID.jpg

    13. Back in SysAid, paste the copied text into the Client ID field.

    14. Set Microsoft Graph permissions in Azure:

      1. In Azure, navigate to Overview > View API permissions.

      2. Click Add Permissions.

      3. Click Select an API.

      4. Select Microsoft Graph.

      5. Select the following permissions from the Application Permissions section:

        • Group.Read.All

        • TeamMember.Read.All

        • User.Export.All

        • User.Read.All

      6. Select the following permissions from the Delegated Permissions section:

        • Group.Read.All

        • GroupMember.Read.All

        • User.Export.All

        • User.Read

        • User.Read.All

        • User.ReadBasic.All

      7. Click Save.

      8. In the Required Permissions section, click Grant permissions.

      9. When prompted, click Yes.
         azureSettingsfilesAPIPermissions.png

    Secret key:

    1. In Azure, under the new SysAid app, go to Manage > Certificates & Secrets.
       azureSettingsfilesDashboard.png

    2. Click +New client secret.

    3. Enter a key name in the description field.

    4. Select the expiration date that suits your security needs.

    5. Click Add.
       azureSettingsfilesAddClientSecret.png

    1. Copy the contents of the key's Value column.

    2. Back in SysAid, paste the copied text into the Secret Key field.

    Domain Name:

    1. In sysAid, enter the domain you want, for example - [Your company name].com.

    2. Click Add.

    3. If you are running SysAid version 20.1.14, enter the following default field mapping text in the JSON field to map.

      {"fieldsMapping":
      [{"sysAidName":"UserName" ,"azureName":"userPrincipalName", "type":"text"},
      {"sysAidName":"FirstName" ,"azureName":"givenName", "type":"text"},
      {"sysAidName":"LastName" ,"azureName":"surname", "type":"text"},
      {"sysAidName":"Location" ,"azureName":"officeLocation", "type":"list"},
      {"sysAidName":"Email" ,"azureName":"mail", "type":"text"},
      {"sysAidName":"Department" ,"azureName":"department", "type":"list"},
      {"sysAidName":"Company" ,"azureName":"companyName", "type":"list"}]}
      

      Feel free to make any changes you like. If you are running SysAid Cloud or a later On-Premise version, see the next section for instructions on mapping fields.

    4. Click Save Changes.

    5. Click the slider to activate the integration.

    It could take up to 12 hours for your Azure fields to be synced with SysAid. Don't edit the integration until the sync is complete.

    Set up Azure as a Secondary User Repository

    If you are using another user depository (such as LDAP) with SysAid, you can select to set up Azure as a secondary user repository within SysAid. This allows you to take advantage of the SysAid features that require Azure integration while still using the user repository that you are most comfortable with. 

    To set up Azure as your secondary SysAid user repository:

    1. Select the Azure is secondary to another User Repository checkbox.

    2. Click Save Changes.