A Microsoft 365 integration enables you to connect your client's apps, services, and data. This article walks you through the essential steps of configuring a Single-tenant Microsoft 365 integration, from ensuring you have the proper prerequisites and licenses to verifying connectivity and syncing user data.

Creating multiple instances

Lifecycle Manager supports setting up multiple instances of the Microsoft 365 single-tenant integration directly through your account. Multiple single-tenant integrations allow you to maintain clear boundaries and proper data governance across client environments.

This separation allows you to:

• Enforce Data Isolation: Keep each client’s data and configurations separate, aiding security and compliance.
• Customize Access: Use unique Azure credentials and permissions for each tenant, enabling tailored integration settings per client.
• Granular Management: Align each tenant’s integration with different policy or licensing needs (e.g., one client might use specific Intune configurations, while another has different requirements).

Integration steps in Microsoft Azure

Creating the Lifecycle Manager application

We recommend creating a dedicated application that Lifecycle Manager uses to access device and software information.

1. Sign in to Microsoft Azure as a Global Administrator.
2. Use the Search resources box to find and select App registrations.
   
    
3. Click +New Registration.
   
    
4. Enter a user-facing display name for the new application registration (for example, Lifecycle Manager Microsoft 365 single tenant Integration).
    
5. Under Supported account types, select Single tenant only.
   Leave the rest of the default settings as is.
    
6. Click Register to create the application.
   
    
7. Note the Application (client) ID and the Directory (tenant) ID under the newly created application. These will be required to complete the integration.
   

Configuring Lifecycle Manager application permissions

Users/admins must grant permissions to applications before they can call APIs. For full functionality, the following permissions are required:

• Microsoft Graph
  • AuditLog.Read.All
  • DeviceManagementApps.Read.All
  • DeviceManagementManagedDevices.Read.All
  • Organization.Read.All
  • Reports.Read.All
  • User.Read.All - The User.Read.All permission is necessary to retrieve user data.
  • ReportSettings.ReadWrite.All
  • SecurityEvents.Read.All

1. Within the created application, expand Manage in the left navigation panel, and click API permissions.
    
2. Click Add a permission.
    
3. In the Request API permissions screen, select Microsoft Graph and then choose Application permissions.
   
    

4. In the Select permissions section, expand the categories listed below and select the documented API permissions.

   Category	Permission required
   AuditLog	AuditLog.Read.All
   DeviceManagementApps	DeviceManagementApps.Read.All
   DeviceManagementManagedDevices	DeviceManagementManagedDevices.Read.All
   Directory	Directory.Read.All
   Organization	Organization.Read.All
   ReportSettings	ReportSettings.ReadWrite.All
   Reports	Reports.Read.All
   SecurityEvents	SecurityEvents.Read.All
   User	User.Read.All

5. Once all permissions are selected, click Add permissions.
    
6. Confirm that the required application permissions show in the Configured permissions section
    
7. Click Grant admin consent for... to add administrator consent for each permission.
    

Granting Lifecycle Manager application access

Client secrets, also known as application passwords, are secret strings the application uses to prove its identity when it requests a token.

1. Within the created application, click Certificates & secrets in the left navigation panel, under Manage.
    
2. In the Client secrets section, click the New client secret button.
   
    
3. Add a description and expiry for the client secret. We recommend 6 months.
    
4. Click the Add button.
    
5. Copy and save the Client secret Value, as this value is required to integrate with Lifecycle Manager.
   
    

Authentication steps

Azure portal authentication

1. Within the created application, click Authentication in the left navigation panel under Manage.
    
2. Under Platform configurations, click Add a platform and choose Web. (If Web already exists, click Add URI)
    
3. Enter the redirect URI as follows:
   • https://app.scalepad.com/account/integration/oauth
      
4. Click Configure
    
5. Under Supported account types, ensure Single Tenant Only is selected.

Adding credentials to Lifecycle Manager

1. Within Lifecycle Manager, navigate to the Microsoft 365 single tenant add integration page and fill in the following information gathered previously:
   • Azure tenant ID
   • Azure application (client) ID
   • Azure Client Secret
     
     
      
2. Click Connect now.
    
3. After the page has been saved, click Authorize, which will open a popup to a Microsoft authorization page to run through.

When you click Connect now, Lifecycle Manager will be set up to receive M365 data.

It can take up to 48 hours for Microsoft 365 data to populate in Lifecycle Manager after a successful integration.

If data is not populating under Assets > Microsoft 365 after 48 hours have elapsed, please contact our Support team.

NEW Join our MSP Power-Ups - Free 15-minute micro-workshops + live Q&A with our Lifecycle Manager experts. Sign up here to reserve your spot.