Azure Marketplace Setup

Connect your Azure Marketplace publisher account to Automatum. This is the Cloud Account connection. You need it to onboard, sync offers, and transact.

Passwordless connection

Automatum connects with Workload Identity Federation. You do not create or store a client secret. Azure trusts Automatum through a federated credential, so there is nothing to rotate and nothing that expires. This matches Microsoft's recommended practice for marketplace automation.

Prerequisites

Before you connect your Azure account, make sure you have:

• An active Microsoft Partner Center account
• Azure Marketplace publisher status (validated tax and payout profiles)
• Your Publisher ID
• Permission to register an app in Azure AD (Microsoft Entra ID)
• Partner Admin access in Partner Center (to add the app and assign a role)
• An Automatum organization

Not a seller yet?

Complete Partner Center enrollment first. See Become a Seller — Azure.

Integration Overview

Automatum uses the Microsoft Partner Center and Marketplace APIs to enable:

• Product listing synchronization
• Private offer creation and management
• Customer entitlement tracking
• Usage reporting for SaaS offers

Step 1: Register an Azure AD Application

1. Sign in to the Azure Portal.
2. Go to Microsoft Entra ID (Azure Active Directory) > App registrations.
3. Click New registration.
4. Enter these values:
   • Name: <Your Company> Marketplace App
   • Supported account types: Accounts in this organizational directory only (Single tenant)
   • Redirect URI: leave blank
5. Click Register.

Placeholder capture — replace with your own before launch.

Step 2: Copy the Application and Tenant IDs

1. Open your new app registration.
2. On the Overview page, copy:
   • Application (client) ID
   • Directory (tenant) ID
3. Keep both values. You paste them into Automatum in Step 5.

Placeholder capture — replace with your own before launch.

Step 3: Add a Federated Credential

This step establishes trust between your Azure app and Automatum. No secret is created.

1. In your app registration, open Certificates & secrets.
2. Select the Federated credentials tab.
3. Click Add credential.

Placeholder capture — replace with your own before launch.

4. Set Federated credential scenario to Other issuer.
5. Enter the values that Automatum shows on the Connect Azure Account screen:

Field	Where to get it
Issuer	Copy from Automatum
Subject identifier	Copy from Automatum
Name	Copy from Automatum
Audience	api://AzureADTokenExchange (Automatum shows this)

6. Click Add.

Placeholder capture — replace with your own before launch.

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.

Production reference values

On the production platform (app.automatum.io) the federated credential uses these values. The Connect Azure Account screen always shows the exact values to copy, but you can confirm them here:

Field	Value
Issuer	https://api.automatum.io
Subject identifier	automatum
Audience	api://AzureADTokenExchange
Name	automatum

Step 4: Add API Permissions

Add these permissions to your app registration under API permissions:

Microsoft Graph (Delegated)

• User.Read — sign in and read the user profile

Partner Center / Marketplace (Application)

• Product Ingestion API access (for listing sync and private offers)

Then click Grant admin consent for [your organization].

TIP

Some Partner Center API access is enabled per account. If a permission is not available, contact Microsoft Partner Center support to enable API access.

Step 5: Grant the App Access in Partner Center

Automatum acts through your Azure AD app. Add the app in Partner Center and give it a role.

1. Sign in to Partner Center.
2. Go to Settings > Account settings > User management.
3. Open the Azure AD applications tab.
4. Click Add Azure AD Application, then Add Azure AD Application.
5. Select the app you created in Step 1.

Placeholder capture — replace with your own before launch.

6. Assign the Manager (Windows) role.
7. Click Add, then confirm the app appears in the list.

Placeholder capture (shows the role list) — select Manager (Windows).

Step 6: Configure in Automatum

1. In Automatum, go to Settings > Cloud Accounts.
2. Click Connect Azure Account.
3. Enter these values:
   • Tenant ID: your Directory (tenant) ID from Step 2
   • Application (Client) ID: from Step 2
   • Publisher ID: from Partner Center
4. Copy the Issuer, Subject, Audience, and Name shown here into the federated credential in Step 3 if you have not done so.
5. Click Test Connection.
6. When the test passes, click Save.

No secret field

Automatum never asks for a client secret. If you added the federated credential correctly, the test connection succeeds with the IDs alone.

Step 7: Sync Products

1. Go to Listings.
2. Click Sync from Azure.
3. Select the offers you want to manage in Automatum.
4. Click Import Selected.

Plan Selection

Azure Marketplace offers can have multiple plans. Automatum imports all plans associated with your offers.

Supported Offer Types

Offer Type	Private Offers	Usage Tracking	Metering
SaaS	✅	✅	✅

Verification

1. Confirm your offers appear in Listings.
2. View an existing private offer.
3. Create a test private offer.
4. Confirm customer entitlements sync correctly.

Troubleshooting

Connection Failed

Error: No matching federated identity record found (AADSTS70021 / AADSTS700213)

• Open Certificates & secrets > Federated credentials.
• Confirm the Issuer, Subject identifier, and Audience match Automatum exactly.
• Confirm the Audience is api://AzureADTokenExchange.

Error: Application not found in directory (AADSTS700016)

• Confirm the Application (Client) ID and Tenant ID are correct.
• Confirm you registered the app in the same tenant you are connecting.

Error: Insufficient privileges

• Confirm you granted admin consent in Step 4.
• Confirm the app has the Manager (Windows) role in Partner Center (Step 5).

Products Not Syncing

No offers found

• Confirm you have published offers in Partner Center.
• Confirm the offers are in Live or Preview status.
• Confirm your Publisher ID is correct.

Partial sync

• Some offer types may not be fully supported yet.
• Check the sync log in Settings > Cloud Accounts > Azure > Sync History.

Private Offers Not Creating

Error: Plan not found

• Confirm the plan ID exists in your offer.
• Confirm the plan is active and published.

Error: Customer not eligible

• Confirm the customer Azure tenant ID is correct.
• Confirm the customer has the necessary permissions.

Azure-Specific Features

Plan Management

Azure offers can have multiple plans with different pricing.

Billing Terms

Supported billing terms for Azure private offers:

• Monthly
• Annual
• Multi-year (up to 3 years)
• Custom durations

Security Best Practices

1. No secrets to manage — federation removes long-lived client secrets.
2. Enable MFA on your Partner Center account.
3. Review audit logs in Partner Center regularly.
4. Limit API permissions to only what you need.
5. Remove the app from Partner Center if you stop using Automatum.

Next Steps

• Create Azure private offers
• Set up SaaS metering
• Set up Azure co-sell
• View Azure analytics

Resources

• Azure Marketplace Documentation
• Partner Center API Reference
• Workload Identity Federation

Need Help?

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