Configuring ReadyWorks as an Azure Enterprise Application: Using Microsoft Graph API as a Data Source

Introduction

This guide details the steps required to configure ReadyWorks as an Azure Enterprise Application, enabling integration with Azure Active Directory (AAD) via the Microsoft Graph API. This document targets IT professionals already proficient with ReadyWorks, Azure, and AAD, seeking to enhance their organization’s asset management capabilities through secure and efficient API integrations.

Setting up ReadyWorks in Azure establishes API connectivity, facilitating secure data exchange between ReadyWorks and your Microsoft tenant. This guide provides configuration instructions, security best practices, and troubleshooting steps.

Important Security Considerations

Please review these security guidelines before proceeding:

• Permissions requested herein are highly privileged, providing extensive access to Azure resources (e.g., users, groups, devices).
• Adhere strictly to the principle of least privilege: consider read-only permissions wherever applicable.
• Securely manage and regularly rotate the client secret following organizational security policies.
• Apply Conditional Access policies to restrict the application’s access according to location, network, or device criteria.
• Regularly audit application activity and permissions via Azure’s monitoring and audit capabilities.

Configuration Steps

1. Register ReadyWorks as an Application in Azure

1. Sign in to Azure Active Directory Admin Center.
2. Navigate to Azure Active Directory > App Registrations.
3. Select New Registration.
4. Enter application details:
   • • Name: Descriptive name (e.g., ‘ReadyWorks Graph Integration’)
     • Supported account types: Accounts in this organizational directory only (Single tenant)
     • Redirect URI: (Leave blank unless specifically required)
5. Click Register.
6. Record the Application (client) ID from the overview page.

2. Configure Microsoft Graph API Permissions

1. From the app’s registration page, select API Permissions > Add a Permission.
2. Select Microsoft Graph, then Application Permissions.
3. Carefully choose permissions aligned to your organization’s needs:

1. After selecting required permissions, click Add Permissions.
2. Click Grant Admin Consent for [Your Organization] and confirm with Yes.
   • • Note: This action impacts tenant-wide; ensure clarity on scope and necessity before proceeding.

3. Generate and Secure Client Secret

1. Select Certificates & Secrets > New Client Secret.
2. Enter a clear description (e.g., “ReadyWorks Graph Client Secret”).
3. Select an appropriate expiration aligned with organizational security requirements.
4. Click Add.
5. Immediately copy and securely store the client secret’s Value. (This is your sole opportunity to access this credential.)

4. Information Required for ReadyWorks Integration

Ensure the following information is securely documented for ReadyWorks connector setup:

• Tenant ID: Azure Tenant ID (found in Azure Active Directory overview)
• Application (Client) ID: From Step 1 registration
• Client Secret: From Step 3 secret generation

Recommended Permissions and Their Uses

Maintenance and Security Best Practices

• Secret Rotation: Proactively rotate client secrets before expiry; schedule reminders accordingly.
• Permission Reviews: Regularly audit permissions to confirm necessity and alignment with current business requirements.
• Access Reviews: Implement periodic access reviews for continued security compliance.
• Monitoring: Activate Azure monitoring tools for auditing and alerts to detect unauthorized or anomalous activity.

Troubleshooting Guidance

If integration issues arise:

• Confirm admin consent for all permissions.
• Verify client secret validity and expiration status.
• Check accuracy of Tenant ID and Application ID in ReadyWorks.
• Confirm sufficient permissions for personnel configuring ReadyWorks.
• Consult Azure AD audit logs for authentication errors or permission issues.
• Open a support ticket with ReadyWorks at: support.readyworks.com

This guide emphasizes secure, minimal-permission integrations aligned with best practices to maximize the utility of ReadyWorks while maintaining rigorous security compliance.