Dashboard shows "organisation does not have an active subscription" after switching to a business Microsoft account – Napster Help

Symptoms

After transferring an Azure subscription from a personal Microsoft account to a business (work) Microsoft account, the Omniagent API dashboard displays the following warning and the API key field is stuck on "Loading":

Dashboard error: "Organisation does not have an active subscription. Companion API requests are currently blocked, and sessions cannot be started."

The Azure subscription itself shows as active and billing ownership has been transferred, but the dashboard does not reflect this.

Root cause

When you first subscribe through the Azure Marketplace using a personal Microsoft account, Napster creates your organisation record linked to that personal email. If you subsequently transfer the Azure subscription to a business account on the Microsoft side, Napster's backend is not automatically notified of this change — the organisation ownership remains tied to the original personal email.

As a result, when you sign in with your business account, the dashboard either finds no matching organisation or finds one with no active subscription attached.

Important: Personal Microsoft accounts are not supported for dashboard access. You must use a business (work or school) Microsoft account to sign in to the Omniagent API dashboard.

Resolution

The recommended fix is to create a new subscription directly from your business Microsoft account, rather than attempting to transfer an existing one. This ensures Napster's backend creates a correctly linked organisation from the outset.

Step-by-step fix

Sign out of the Omniagent API dashboard completely.
Go to the Azure Portal and sign in using your business Microsoft account (not a personal @outlook.com or @hotmail.com address).
Search for Napster Companion API in the top search bar and navigate to the service page.
Click + Create and fill in your subscription details. Set the region to (US) East US.
After deployment completes, click Go to resource, then click Go to Napster Companion API to open the dashboard via the Azure resource link — do not navigate directly to the dashboard URL.
You should now land in the correct organisation with an active subscription. Proceed to create your API key from the dashboard.

Note: If the Napster Companion API does not appear in your Azure Portal search, your subscription may need to be allowlisted. Contact Napster support to request access, as the service is currently in preview.

Additional notes

Do not use the old personal-account organisation for any further development. API keys and project configurations created under a personal-account organisation cannot be migrated to a new one — you will need to recreate companions, projects, and keys under the new business-account organisation.

Confirmed fix: Creating a fresh subscription directly under the business Microsoft account resolves the subscription warning and unblocks API access.