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": "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.
Important: Personal Microsoft accounts are not supported for dashboard access. You must use a business (work or school) Microsoft account.
Resolution
The Napster Omniagent API is now in public preview on the Azure Marketplace — no prior allowlisting or support approval is needed. The recommended fix is to create a new subscription directly from your business Microsoft account by following the setup guide.
Step-by-step fix
- Sign out of the Omniagent API dashboard completely.
- Sign into the Azure Portal using your business Microsoft account.
- Follow the Azure resource setup guide to create a new Napster Omniagent API resource.
- Once deployment completes, click Go to Napster Companion API from the resource page — this links the correct organisation to your new subscription.
- Go to API Keys in the dashboard to generate your key.
Note: Do not use the old personal-account organisation for further development. API keys and projects under it cannot be migrated to the new one.
Confirmed fix: Creating a fresh subscription directly under the business Microsoft account resolves the subscription warning and unblocks API access.