Publishing to the Azure Government Marketplace

This article is provided to help partners create, deploy, and manage their solutions listed in the Azure Government Marketplace for Azure Government customers and partners to use.

Why publish to Azure Government

Azure Government is a dedicated instance of Azure that employs world-class security and compliance services critical to U.S. government for all systems and applications built on its architecture. This makes the cloud a viable option for thousands of US federal, state, local and tribal governments, and their partners.

Publishing your solution in the Azure Government Marketplace is as simple as publishing to Azure global and checking an extra box. There are no compliance requirements to publish your solution to Azure Government and making it available in the Azure Government Marketplace makes it easier for these government customers to gain exposure to your solution and get up and running quickly.

Compliance considerations

There are no initial Microsoft compliance requirements to publish solutions to the Azure Government Marketplace.

Once a solution has been published, customers can deploy it into their own subscription as part of a broader operational environment or business solution. The customer might then opt to certify the overarching environment. As part of that certification process, they might reach out to the publisher with extra requirements, which the publisher can then evaluate and triage with the customer.

Marketplace offer support

Currently, the Azure Government Marketplace only supports the following offer types:

  • Virtual Machines > Bring your Own License
  • Virtual Machines > Pay-as-you-Go
  • Azure Application > Solution Template / Managed App
  • Azure containers > Bring your Own License
  • IoT Edge modules > Bring your Own License

If there are other offer types you'd like to see supported in Azure Government, let us know via the Azure Government feedback forum.



These steps assume you have already published a solution in Azure Global. If you haven't, please check out the Azure Marketplace Publisher Guide documentation before proceeding.

  1. Sign in to the Partner Center Portal.
  2. Navigate to the Commercial Marketplace program.
  3. Open the offer you want to publish to the Azure Government Marketplace.
  4. Go to the Plan overview page using the left menu.
  5. Click on the plan you want to update to be available in Azure Government.
  6. In the Plan setup page, under Azure regions, check the Azure Government box. Remember that this option isn't available for all offers.
  7. Optionally, click the + Add Certification link to add links to any certifications that are relevant for your product and that you want to make available to customers.
  8. Optionally, add your Azure Government subscription to preview your marketplace offering before it is broadly available.
    1. Click on Preview audience entry in the offer-level left menu.
    2. Add your Azure Government subscription ID.
  9. Publish your solution once again.


If you want to confirm that your solution has been published or test it, you need to request an Azure Government account. This is a separate account from any account in Azure Global that is used to log in to the Azure Government portal.

To obtain an account:

  1. Request an Azure Government trial account.
    • Indicate that your organization is a Solution Provider Serving U.S. Federal, State, Local or Tribal Government Entities.
  2. Wait for 3 - 5 business days for your account to be provisioned.
  3. Log in to the Azure Government portal with your newly created account.
  4. Eventually you can convert your trial account to a paid account


Generally, virtual machines and solution templates work across both Azure and Azure Government, however there are a few instances when this is not the case. The following section outlines the most common reasons why a virtual machine or solution template would work in the Azure Marketplace but not the Azure Government Marketplace.

Not available after publish

If you've completed all the steps outlined above and your virtual machine is still not available in the Azure Government Marketplace, make sure that your Virtual's Machine Hide this SKU setting is not set to Yes. If it is set to yes, there's probably also a solution template that you also need to publish to Azure Government. If there is no solution template and you want to make the standalone Virtual Machine available, flip that switch to No and republish.

Hardcoded endpoints

Verify endpoints are not hard-coded into your solution Template for Azure Global as they will not be valid for any other Azure clouds (Azure Government, Azure China, Azure Germany). Instead modify the Solution template to obtain the endpoint from the resource, for example:

  • Incorrect VHD uri (hard coded)

    "uri": "[concat('https://', variables('storageAccountName'), '',  '/osdisk.vhd')]",
  • Correct VHD uri (referenced)

    "uri": "[concat(reference(resourceId('Microsoft.Storage/storageAccounts/', variables('storageAccountName'))).primaryEndpoints.blob, 'osdisk.vhd')]",

Hardcoded list of locations

Make sure your solution template supports the Azure Government locations.

Unavailable resources

Verify that resources, API versions, extensions and VM images used in your solution template are available in Azure Government.


Make sure that the image that your solution template relies on is available in Azure Government. If this is a Virtual Machine you own, need to also publish that to the Azure Government Marketplace. Check out the Azure Government Marketplace images documentation to obtain the list of images available.

Resource providers and API versions

You can obtain the full list of resource providers and their API versions by logging in to the Azure Government portal using your Azure Government account and following the steps listed in the Resource providers and types documentation.


Make sure that any virtual machine extensions that your solution template relies on are available in Azure Government. Check out the Azure Government virtual machine extensions documentation to obtain the list of extensions available.

Next steps