Project (Microsoft)
Best Practice:
Microsoft Project is a project management application. It is designed to assist a project manager in developing a schedule, assigning resources to tasks, tracking progress, managing the budget, and analyzing workloads.
The following sections explain prerequisites, resources, and instructions for integrating with SaaS Management.
• | Stored Project (Microsoft) Information |
• | Required Minimum Permissions for Project (Microsoft) |
• | Project (Microsoft) Authentication Method |
• | Required Project (Microsoft) Credentials |
• | Data Anonymization for Project (Microsoft) |
• | Integrating Microsoft Project With SaaS Management |
• | Project (Microsoft) API Endpoints |
Stored Project (Microsoft) Information
The following table describes the available integration tasks and stored data within SaaS Management.
Available Integration Tasks |
Information Stored |
|||||||||||||||
Application Roster |
|
|||||||||||||||
Application Access |
|
Note:The information stored is subject to change as enhancements are made to the SaaS application.
Required Minimum Permissions for Project (Microsoft)
The minimum API required permissions are based on the Required Application Permissions for Project (Microsoft) and the Required User Role for Project (Microsoft).
Required Application Permissions for Project (Microsoft)
Application Permission |
Description |
Integration Task Name |
Directory.Read.All |
Enables you to read the list of users in your Microsoft account. |
Application Roster |
AuditLog.Read.All |
Enables you to read the audit log details in your Microsoft account. |
Application Access |
Offline_access |
Enables you to generate the refresh token. |
|
Required User Role for Project (Microsoft)
Note:The following SaaS application user role is not applicable to Flexera One roles.
User Role |
Description |
Application Administrator |
To grant the application permissions, the user must have Application Administrator access. For more information, see Microsoft’s description of the Application Administrator. |
Note:Consider the following:
• | After 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. |
• | To fetch sign-in events: |
• | You must have an Azure AD Premium P1 or Premium P2 license assigned per tenant. For more information, see Microsoft’s documentation topic, Microsoft Entra Plans & Pricing. |
• | You must ensure the Office 365 audit log is turned on. For more information, see Microsoft’s documentation topic, Turn Auditing On or Off. |
Project (Microsoft) Authentication Method
The required authentication method is OAuth 2.0 With Authorize Flow. For more information, see Microsoft’s documentation topic, Microsoft Identity Platform and OAuth 2.0 Authorization Code Flow.
Required Project (Microsoft) Credentials
The following credentials are required:
• | Username |
• | Password. |
Note:Username and Password are required only for authorizing the application permissions. These values are not stored in SaaS Management.
Data Anonymization for Project (Microsoft)
Data anonymization is the processing technique that removes or modifies identifiable information. After 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 Microsoft Project application, it is important to make sure that anonymized users are not imported from Microsoft Project 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 Microsoft Project 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 Microsoft Project With SaaS Management. |
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 Microsoft’s documentation topic, Microsoft 365 Reports Show Anonymous User Names Instead of Actual User Names. If anonymized user data has been imported after integrating Office 365 with SaaS Management, submit a Support Case.
Integrating Microsoft Project With SaaS Management
Complete the following steps to integrate Microsoft Project with SaaS Management.
To integrate Microsoft Project with SaaS Management:
1. | In SaaS Management, add the Office 365 application. For more information, see 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. |
Note:All blocked users will be displayed as normal users in SaaS Management.
Project (Microsoft) API Endpoints
Application Roster
https://graph.microsoft.com/v1.0/users
Application Access
https://graph.microsoft.com/v1.0/auditLogs/signIns
Note:Due to the limitations in Microsoft Graph APIs, we are not able to capture Suspicious Activities for the Microsoft Project integration.