Office 365

Best Practice:Flexera recommends creating the Microsoft 365 integration to view your organization’s Office 365, Dynamics 365, Power BI, Project, and Visio license usage data. Any existing Office 365, Dynamics 365, Power BI, Project, and Visio integrations in SaaS Management will be superseded by this new Microsoft 365 integration. To deactivate an existing integration, refer to Avoiding Duplicate Microsoft 365 Licenses between SaaS Management and IT Asset Management.

Office 365 is a cloud-based service that is designed to help meet your organization's needs for robust security, reliability, and user productivity.

Information Stored
Minimum Permissions Required
Authentication Method
Credentials Required
License Types
Data Anonymization
Integrating Office 365 with SaaS Management
Auto-Populated Office 365 License Information
API Endpoints

Information Stored

The following table describes the available integration tasks and stored data.

Available Integration Tasks

Integration Task

Information Stored

Application Roster

User ID (User Principal Name)
First Name
Last Name
Active Date
Deactivated Date
Assigned Licenses

Application Access

Last Activity Date of the following applications:

Microsoft Exchange Server
Microsoft Teams
Skype for Business

Note:Application Access data is available 3 days after the event(s) occurs. Therefore, the data in the Microsoft Portal may not match the data in SaaS Management for application access.

License Differentiation

See License Types and Tracking Application Activity by License Type for License Differentiation.

License Information

License Name
License Type
Purchased Quantity

Note:The above license information is retrieved every 24 hours. Therefore, the data in the Microsoft Portal may not match the data in SaaS Management for license information.


Reclaiming SaaS licenses affects all of the user’s licenses within a SaaS integration. For example, a user has licenses for Office 365 Exchange, Outlook, and Yammer. However, the Software Asset Manager is only managing licenses for Office 365 Exchange and Outlook. Reclamation removes all three (Office 365 Exchange, Outlook, and Yammer) licenses from the user.

To reclaim Office 365 SaaS licenses, refer to Reclaiming SaaS Licenses.

Note:The information stored is subject to change as enhancements are made to the product.

Minimum Permissions Required

Minimum API required permissions are based on the Application Permission and User Role .

Application Permission

Application Permission



Integration Task Name


To read the list of users in your Microsoft account

Application Roster, License Information


To read the user access event details in your Microsoft account

Application Access


This permission is required to modify the license assigned to the user.



This permission is necessary for the refresh token generation.


User Role

User Role



Application Administrator

To grant the application permissions, the user must have Application Administrator access. For details, refer to Microsoft’s description of the Application Administrator.

Reports Reader

This role is required for retrieving the Office 365 activities report details.

License Administrator

This role is necessary for user license management in the reclamation task.

Note: Note the following:

Once the Authorization is completed and the integration tasks are executed successfully, the user role can be reduced to the Report Reader role.
After Authorizing, changing the password or revoking the user roles for the user used for authorizing will result in an integration task failure.

Authentication Method

OAuth2 with Authorize flow. For details, refer to the Microsoft OAuth2 authorization code flow documentation.

Credentials Required


Note:These credentials are required only for authorizing the application permissions. They are not stored in SaaS Management.

License Types

To learn more about the product names and service plan identifiers for Office 365 licenses, refer to 

Data Anonymization

Data anonymization is the processing technique that removes or modifies identifiable information. Once the process is complete, data cannot be associated with a specific user. It helps protect private and sensitive data as well as private activities while maintaining its integrity.

When adding the Office 365 application, it is important to make sure that anonymized users are not imported from Office 365 into SaaS Management. You will need to access reports that provide information about your organization’s use of applications and services.

The following procedure is important as a prerequisite to ensure that anonymized user data is not imported when integrating Office 365 with SaaS Management.

To view reports with anonymized user data:

1. Sign in to the Microsoft 365 Portal Admin Center.
2. In the menu, go to Settings > Org settings and click the Services link at the top.
3. Scroll down and click Reports.
4. In the window that is displayed, clear the Display concealed user, group, and site names in all reports box.
5. Proceed to Integrating Office 365 with SaaS Management.

Note:Ensure that data anonymization is disabled in your Microsoft account. Otherwise, all activity data will end up in Suspicious SaaS Activities. For more information, see the Microsoft documentation regarding Showing Anonymous User Names. If anonymized user data has been imported after integrating Office 365 with SaaS Management, submit a Support Case.

Integrating Office 365 with SaaS Management

To integrate Office 3656 with SaaS Management, perform the following steps:

To integrate Office 365 with SaaS Management:

1. In SaaS Management, add the Office 365 application. Refer to Adding an Application.
2. Click Authorize, which will redirect you to the Microsoft portal.
3. In the Microsoft portal, enter your Application Administrator username and password to sign in.
4. In the Microsoft Permissions requested window, click Accept to authorize and provide access to the account for the APIs used in the integration.

5. For further information on managing and optimizing your organization’s Office 365 licenses, refer to:
Auto-Populated Office 365 License Information
Tracking Application Activity by License Type for License Differentiation
Reclaiming SaaS Licenses.

Note:All blocked users will be displayed as normal users in SaaS Management.

Auto-Populated Office 365 License Information

The SaaS Management integration with Office 365 offers a License Information integration task that automatically retrieves every 24 hours the name of the Office 365 plan, license type, and total allowed number of licenses. This auto-populated Office 365 license information provides a more complete view of your Microsoft SaaS entitlements and component usage by displaying:

Assigned entitlements.
User’s license activity (based on the user’s last login) for O365 Exchange, O365 OneDrive, O365 SharePoint, O365 Skype, O365 Yammer, O365 Teams, and O365 Outlook.
A 7 Services filter in the Office 365 Activity tab, which helps you narrow the focus of your organization’s Office 365 license activity.

Important:If you enable the License Information integration task, you need to enter and keep up to date the following Licenses Tab information. The License Information integration task does not pull in this information. The SaaS application’s annual spend calculation relies on entered and accurate license effective and ending dates.

Effective Date 
Ending Date 
Payment Frequency 

To auto-populate Office 365 license information, refer to Auto-Populating SaaS Application License Information. When the License Information integration task is enabled, the License type, Name, and # of Items Allowed fields in the Office 365 Licenses tab are disabled as this information is automatically populated. The active and inactive ingested license data from Microsoft can be compared against the Subscriptions data from the Licenses menu of the Microsoft 365 Admin Center.

API Endpoints

Application Roster

Application Access

License Information

Reclamation{id | userPrincipalName}/assignLicense