Skip to content

Azure Co-Sell Setup

Connect Automatum to Microsoft Partner Center referrals. This is the Integrations → Microsoft connection (Part 2 of 2). You need it to send and receive co-sell opportunities with Microsoft field sellers.

Part 2 of 2

Set up the Cloud Account (transact) app first. See Azure Integration (Start Here) for the full picture.

Co-sell uses its own app registration

Automatum uses two Azure AD apps. The Cloud Account app transacts and syncs offers (Azure Marketplace Setup). The Co-Sell app on this page is a second, dedicated app for Microsoft referrals. Register a separate app for co-sell — it needs extra API permissions and a redirect URI that the transact app does not. Set up the Cloud Account first.

Passwordless connection

Co-sell also uses Workload Identity Federation. You do not create or store a client secret.

Prerequisites

Before you connect co-sell, make sure you have:

  • A connected Azure Cloud Account in Automatum (Azure Marketplace Setup)
  • Your Microsoft Partner Network (MPN) ID
  • Referrals Admin access in Partner Center
  • A co-sell-eligible solution configured in Partner Center
  • Permission to register an Azure AD app
  • A Global Administrator (or Privileged Role Administrator) to grant admin consent for the app

Co-sell eligibility

Your solution must reach co-sell-ready status in Partner Center before Microsoft shares referrals. See Microsoft: Configure co-sell.

Step 1: Register the Co-Sell Azure AD Application

Register a dedicated app for co-sell. Keep it separate from your Cloud Account (transact) app — the co-sell app needs the extra API permissions and redirect URI below.

  1. Sign in to the Azure Portal.
  2. Go to Microsoft Entra ID > App registrations.
  3. Click New registration and enter:
    • Name: <Your Company> Co-Sell App
    • Supported account types: Accounts in this organizational directory only (Single tenant)
    • Redirect URI: platform Web, value https://api.automatum.io/integration/azure-partner-center/callback
  4. Copy the Application (client) ID and Directory (tenant) ID from the Overview page.

Use the Web platform for the redirect URI

Add the redirect URI under Authentication > Add a platform > Web. Do not use Single-page application — the authorize step then fails with "endpoint only accepts POST" (AADSTS900561).

Co-sell uses delegated Partner Center permissions. Automatum calls the Partner Center Referrals API as the integration user you invite in Step 4.

  1. In your app registration, open API permissions.
  2. Click Add a permission > APIs my organization uses.
  3. Add each of these permissions:
APIApp (client) IDPermissionType
Microsoft GraphUser.ReadDelegated
Microsoft Partner4990cffe-04e8-4e8b-808a-1175604b879fuser_impersonationDelegated
Microsoft Partner Centerfa3d9a0c-3fb0-42cc-9193-47c7ecd2edbduser_impersonationDelegated
Microsoft Partner Center (Legacy)fabfbdc4-5751-471c-ac43-3826fa1afc31user_impersonationDelegated

Cannot find the API by name

Search by the application (client) ID shown in the table above. "Microsoft Partner" can also appear as "Microsoft Dev Center". The two Partner Center apps do not resolve to a friendly name — paste the ID.

  1. For each API, select Delegated permissions, check the permission (user_impersonation, or User.Read for Microsoft Graph), then click Add permissions.

Now grant admin consent so users are never prompted:

  1. Back on the API permissions page, above the Configured permissions list, click Grant admin consent for [your organization] (next to + Add a permission).
  2. In the confirmation dialog, click Yes.
  3. Confirm the Status column shows a green check Granted for [your organization] for every permission.

Azure app — API permissions with admin consent granted

Admin consent is required

Only a Global Administrator or Privileged Role Administrator can grant admin consent. Without it, the connection fails with an insufficient-privileges or consent error.

Step 3: Add a Federated Credential

  1. In the app registration, open Certificates & secrets.
  2. Select the Federated credentials tab.
  3. Click Add credential and set the scenario to Other issuer.
  4. Enter the Issuer, Subject identifier, Name, and Audience that Automatum shows on the Integrations → Microsoft card, then click Add.

Azure app — Add a federated credential

Production reference values

On the production platform (app.automatum.io) the federated credential uses these values. The Integrations → Microsoft card always shows the exact values to copy, but you can confirm them here:

FieldValue
Issuerhttps://api.automatum.io
Subject identifierautomatum
Audienceapi://AzureADTokenExchange
Nameautomatum

Copy the values exactly

Azure matches the incoming token on Issuer, Subject, and Audience. A single extra space breaks the connection. Use the copy button in Automatum for each field.

Step 4: Invite the Automatum Integration User

Automatum uses a dedicated integration user to read and write referrals.

  1. Sign in to Partner Center.
  2. Go to Settings > User management.
  3. Click Add user > Invite outside users.
  4. Enter the email address that Automatum shows on the co-sell card.

Partner Center — Add user

  1. Assign the Referrals Admin role (scoped to your entire organization).

Partner Center — assign a role to the user

  1. Click Invite (or Save).

Step 5: Add the Azure AD Application in Partner Center

  1. In User management, open the Azure AD applications tab.
  2. Click Add Azure AD Application and select your app from Step 1.
  3. Assign the Referrals Admin role.
  4. Click Add, then confirm the app appears in the list.

Step 6: Authorize and Connect in Automatum

  1. In Automatum, go to Settings > Integrations > Microsoft.
  2. Enter the Application (Client) ID and Directory (Tenant) ID.
  3. Click Authorize. Sign in with the integration user you invited in Step 4.
  4. Review the requested permissions, then click Accept.
  5. Return to Automatum and click Test Configuration.

Permissions can take time

Partner Center permission changes can take up to 24 hours to apply. If the test fails right after setup, wait and try again.

Step 7: Add Co-Sell Solutions

  1. In Partner Center, open your co-sell-eligible solution.
  2. Copy the Solution Name and Solution ID.
  3. In Automatum, add the solution under Integrations → Microsoft.

What Automatum Syncs

  • Referrals you send to Microsoft
  • Referrals Microsoft shares with you
  • Opportunity status updates
  • Solution mapping for co-sell deals

See Co-Sell Overview for how to manage opportunities.

Troubleshooting

Authorize Fails

  • Confirm you signed in with the invited integration user, not your own account.
  • Confirm the user has the Referrals Admin role.
  • Confirm you granted admin consent for the app permissions (Step 2).

No Matching Federated Identity (AADSTS70021)

  • Confirm the Issuer, Subject identifier, and Audience match Automatum exactly.
  • Confirm the Audience is api://AzureADTokenExchange.

Referrals Not Appearing

  • Confirm your solution is co-sell-ready in Partner Center.
  • Wait up to 24 hours for permissions to apply.
  • Confirm the Solution ID in Automatum matches Partner Center.

Need Help?

Contact support@automatum.io or use the in-app chat for help with Azure co-sell.

Automatum GTM Platform