Skip to main content

Project Client Credentials (Microsoft)

tip

Project Client Credentials is no longer available when selecting Add Application on the Managed SaaS Applications page. Use instead the Microsoft 365, Microsoft 365 Certificate Based Authention, or Microsoft 365 Client Credentialsintegration to view your organization’s Office 365 Client Credentials, Dynamics 365 Client Credentials, Power BI Client Credentials, Project Client Credentials, and Visio Client Credentials license usage data. To deactivate an existing integration, see Avoiding Duplicate Microsoft 365 Client Credentials Licenses between SaaS Management and IT Asset Management.

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.

info

This Project (Microsoft) Client Credentials integration requires the authentication method OAuth2 with client credentials.

The following sections explain prerequisites, resources, and instructions for integrating with SaaS Management.

Stored Information for Project (Microsoft) Client Credentials​

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

Available Integration TasksInformation Stored
Application RosterUser ID (User Principal Name)
Email
First Name
Last Name
Active Date
Application AccessUser ID (User Principal Name)
Last Login
note

The information stored is subject to change as enhancements are made to the SaaS application.

Required Minimum Permissions for Project (Microsoft) Client Credentials​

The minimum API required permissions are based on the Required Application Permissions for Project (Microsoft) Client Credentials and the Required User Role for Project (Microsoft) Client Credentials.

Required Application Permissions for Project (Microsoft) Client Credentials​

Application PermissionDescriptionIntegration Task Name
Directory.Read.AllEnables you to read the list of users in your Microsoft account.Application Roster
AuditLog.Read.AllEnables you to read the audit log details in your Microsoft account.Application Access

Required User Role for Project (Microsoft) Client Credentials​

note

The following SaaS application user role is not applicable to Flexera One roles.

User RoleDescription
Global AdministratorTo grant the application permissions, the user must have Global Administrator access. For more information, see Microsoft’s documentation topic, Microsoft Entra Built-In Roles.
note

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.

Authentication Method for Project (Microsoft) Client Credentials​

The required authentication method is OAuth 2.0 With Client Credentials. For more information, see Microsoft’s documentation topic, Microsoft Identity Platform and the OAuth 2.0 Client Credentials Flow.

Required Credentials for Project (Microsoft) Client Credentials​

The following credentials are required:

  • Client ID

  • Client Secret

  • Tenant ID.

Obtaining Client Credentials and Tenant ID for Project (Microsoft) Client Credentials​

To obtain client credentials and tenant ID, perform the following steps.

  1. Login to your Microsoft Azure Portal.
  2. In the Search box at the top of the page, enter App registrations and click App registrations in the search results to select it. The App registrations page opens.
  3. Click New Registration. The Register an application page opens.
  4. Enter a Name and choose the Accounts in this organizational directory only option.
  5. Click Register.
  6. On the Overview tab, copy the Application (client) ID and copy the Directory (tenant) ID to a location you can access later. You will need these values in Integrating Microsoft Project Client Credentials With SaaS Management.
  7. To generate a Client secret, do the following:
    1. Click the Certificates & secrets tab.
    2. Under Client secrets, click New client secret. The Add a client secret dialog box opens.
    3. In the Description field, enter a name for the new secret.
    4. Under Expires, choose an expiration value.
    5. Click Add.
    6. Under Client secrets, copy the client secret value. You will need this in Integrating Microsoft Project Client Credentials With SaaS Management.
  8. Click the API permissions tab and do the following:
    1. Click Microsoft Graph. The Request API permissions panel opens.
    2. Click Application permissions.
      note

      Do not select Delegated permissions. Delegated permissions will not work.

    3. In the Select permissions search box, enter AuditLog and then click the arrow to expand AuditLog, and select the AuditLog.Read.All permission checkbox.
    4. In the Select permissions search box, enter Directory and then click the arrow to expand Directory, and select the Directory.Read.All permission checkbox.
    5. Click Update permissions.
  9. After the permissions are added, grant admin consent.
  10. Complete Integrating Microsoft Project Client Credentials With SaaS Management.

Data Anonymization for Project (Microsoft) Client Credentials​

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 Client Credentials application, it is important to make sure that anonymized users are not imported from Microsoft Project Client Credentials 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 Client Credentials 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 Client Credentials 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 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 Microsoft Project Client Credentials with SaaS Management, submit a Support Case.

Integrating Microsoft Project Client Credentials With SaaS Management​

Complete the following steps to integrate Microsoft Project Client Credentials with SaaS Management.

To integrate Microsoft Project Client Credentials with SaaS Management:

  1. In the Microsoft admin portal, enter your Global Administrator username and password to sign in.
  2. From your Microsoft account, copy the Client ID, Client Secret, and Tenant ID values.
  3. In SaaS Management, Add the Project (Microsoft) Client Credentials application. For more information, see Adding an Application.
  4. In the Add Application page for Project Client Credentials:
    1. Select the Application Roster and Application Access integration tasks checkboxes.
    2. Paste the values copied into the Client ID, Client Secret, and Tenant ID fields.
    3. Click Authorize.
    note

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

API Endpoints for Project (Microsoft) Client Credentials​

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.