Introduction
Welcome to the set of instructions on how to configure ReadyWorks as an Enterprise application in Azure to integrate with Azure Active Directory (AAD). This guide is designed for IT professionals familiar with ReadyWorks, Azure, and AAD. It is intended for those specifically seeking to enhance their organization's asset data within ReadyWorks.
Creating an Enterprise app in Azure to support ReadyWorks involves establishing API connectivity to the necessary tenant and resources, enabling seamless integration between the two platforms. By following the steps outlined in this guide, you will be able to configure the new application, granting it access to the Microsoft Graph API, and capture essential information for the successful configuration of the ReadyWorks connector. As you proceed, ensure that you have the appropriate administrative privileges within Azure and ReadyWorks to complete the required tasks.
Let's get started and unlock the full potential of ReadyWorks in combination with Azure, empowering your organization to efficiently manage IT projects and leverage the advanced features offered by both platforms.
We’ll begin by signing into the Azure Active Directory admin center and proceeding with the step-by-step instructions to create the ReadyWorks Enterprise application and then grant it access to the Microsoft Graph API.
Configuration Guidance
1. Create a ReadyWorks app as a native app in Azure
Create a new enterprise application for ReadyWorks which will allow the ReadyWorks connector to establish API connectivity to the tenant/resources needed.
- Sign in to the Azure Active Directory Administration Center.
- Choose Azure Active Directory > App Registrations to open the App registrations pane.
- Select New App Registration.
- Type the app details.
- Type a friendly name, such as ‘ReadyWorks AAD Graph API’ for the Name.
- Select Accounts in this organizational directory only (Microsoft only - Single tenant) for the Supported account types.
- Select Register.
- Note the Application (client) ID of this app. You will need this later for the ReadyWorks connector configuration.
2. Grant the new enterprise app access to the Microsoft Graph API
You now have an app defined in Azure. Grant access from the native app to the Microsoft Intune API.
- Sign in to the Azure Active Directory Admin Center.
- Choose Azure Active Directory > App Registrations to open the App Registrations pane.
- Select the app that you need to grant access. Named the app ReadyWorks.
- Select API Permissions > Add a Permission.
- Find and select the Microsoft Graph API. It is named Microsoft Graph API.
- Select Application Permissions box, scroll down and expand the “Device” section and check the “Device.ReadWrite.All” box.
- Continue scrolling down and expand the “Group” section and check the “Group.ReadWrite.All” box.
- Continue scrolling down and expand the “GroupMember” section and check the “GroupMember.ReadWrite.All” box.
- Continue scrolling down and expand the “User” section and check the “User.ReadWrite.All” box.
- Click Add Permissions.
- Select Grant Admin Consent for Microsoft in the Configured permissions pane, then select Yes. This will grant access to all accounts in the current directory. This will prevent the consent dialog box from appearing for every user in the tenant. For more information, see Integrating applications with Azure Active Directory.
- Select Certificates & Secrets > + New Client Secret and generate a new secret. Give it a descriptive name such as “ReadyWorks AAD Graph Client Secret”, choose your preferred expiration period, and click the “Add” button. Important: Copy and paste the client secret Value immediately before leaving this screen – this is the only opportunity you will have to copy it – otherwise you will need to delete and re-create a new secret. Keep this information handy because it will be needed later for the ReadyWorks connector configuration.
3. Information needed for ReadyWorks Integration
After creating the ReadyWorks app in Azure, be sure to capture the following information which will be needed in the connector configuration options.
- Tennant ID – This is your organizations Azure Tenant ID.
- Application (client) ID which was configured in Step 1.
- Secret which was configured in Step 2.