PingOne

Adding Microsoft 365 to the PingOne application portal

Use the application catalog to add Microsoft 365 to your application portal.

Before you begin

You must have a Microsoft Azure account with a custom domain configured in Microsoft Entra ID.

The IssuerURI value that PingOne provides during application configuration must be unique in Microsoft Azure. This means that two domains or subdomains within a single Azure account can’t be connected to the same PingOne Microsoft 365 application.

About this task

PingOne supports the Microsoft 365 passive and active profiles for . Passive profile enables web browser SSO, while active profile is used by native clients, such as mobile devices and email clients. To authenticate with an active profile, users must provide their PingOne username and password to the client. Microsoft verifies these credentials with PingOne using the WS-Trust protocol.

If the PingOne environment is configured with an gateway, these credentials can be validated against Entra ID. Learn more in Gateways.

Steps

  1. In the PingOne admin console, go to Applications > Application Catalog.

  2. In the Search for applications bar, enter Microsoft 365.

  3. Click the Microsoft 365 entry to open the details panel.

  4. On the Quick Setup page, review the following:

    • Name (optional): Enter a new name to replace the default application name.

    • Icon (optional): Select a new image to replace the default application icon.

    • Domain Name: Enter the <Custom Domain> value from your Entra ID account. You can find your <Custom Domain> in the Microsoft Entra admin center by going to Identity > Settings > Domain Names.

    • Subject NameIdentifier Format: Select the value in the list to use for the Subject NameIdentifier attribute in the WS-Federation security token.

      Possible values are urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress (default) or urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.

      If the application is already configured, click View in Applications list to view the full configuration.

  5. Click Next.

  6. On the Map Attributes page, select the PingOne attributes to map to the required ImmutableID, Subject, and UPN Microsoft 365 attributes.

    ImmutableID uniquely identifies a user in Entra ID. You can find the ImmutableID value by running the Get-MsolUser command in PowerShell after you configure federation with Entra ID. Learn more about Get-MsolUser in the Microsoft documentation.

    For Subject, the mapping attribute defaults to Email Address but can be configured to a different value.

    For UPN, use an email address with a domain name that matches the domain name registered with Microsoft 365.

    • If your user identities are stored in the PingOne Directory, use the default mapping of ImmutableID to ExternalID. ExternalID is the user’s User ID in PingOne.

    • If the Microsoft 365 users are migrated into PingOne from Entra ID through the LDAP gateway, and the source of the ExternalID is objectGUID or ms-DS-ConsistencyGuid, add an expression to the mapping configuration. Locate the ImmutableID mapping, and click the Gear icon to open the expression builder. Enter the following expression:

      #string.uuidAsBase64Guid(user.externalId,null)

      Learn more in Using ms-DS-ConsistencyGuid as sourceAnchor in the Microsoft documentation.

    • You can create a custom PingOne user attribute instead of using ExternalID. Map objectGUID or ms-DS-ConsistencyGuid as the attribute source. Locate the ImmutableID mapping, and click the Gears icon to open the expression builder. Enter the following expression:

      #string.uuidAsBase64Guid(user.customAttrName,null)

      where customAttrName represents the custom PingOne user attribute. You can also replace null with a custom value, such as an error.

  7. Click Next.

  8. On the Select Groups page, click the name of the user groups that you want to have access to the application. You can browse or search for groups. Click the Added tab to see the groups that currently have access to the application.

    By default, all users have access to the application. Assigning groups restricts application access to those groups only.

  9. Click Save.

  10. Click the View in Applications list link.

  11. Click the Overview tab.

  12. Determine which cmdlets to use.

    Choose from:

    • If you’ve upgraded to Graph PowerShell, locate the Microsoft Graph PowerShell cmdlets.

    • If you haven’t upgraded to Graph PowerShell, locate the MSOnline cmdlets.

  13. Do one of the following:

    Choose from:

    • If you’re setting up identity federation settings for the first time to use PingOne as the identity provider, locate either Microsoft Graph PowerShell cmdlets or MSOnline cmdlets, depending on your configuration. Click the Copy to clipboard icon for the appropriate section.

    • If you’re updating existing identity federation settings to use PingOne as the identity provider, locate the Execute following cmdlets in PowerShell to change existing federation settings section. Click the Copy to clipboard icon.

      You might have to scroll to the right to see the Copy to clipboard icon.

      You might have to collapse the Microsoft Graph PowerShell cmdlets entry to see the MSOnline cmdlets entry.

  14. Open Windows PowerShell.

  15. In PowerShell, paste the copied commands and run them.

    These commands update the domain authentication in Entra ID to SSO.

    Learn more about the Microsoft cmdlets that are used in PingOne in the following topics in the Microsoft documentation:

Next steps

You can optionally enable Kerberos authentication for Microsoft 365 applications. Learn more in Enabling Kerberos authentication.

After you configure the application, you can manage it from Applications > Applications. Learn more in Editing an application.