How can I move my Azure Marketplace purchases from my MOSP subscription to my direct Enterprise Agreement (EA) subscription?

Although most Microsoft subscriptions can be easily converted to your Enterprise Agreement, Azure Marketplace purchases within those subscriptions cannot.

To migrate Virtual Machines (VMs) purchased from the Azure Marketplace to your Enterprise Agreement subscription, you will need to delete them within your existing MOSP subscription and deploy them again within your EA subscription.

To migrate other services purchased from the Azure Marketplace to your EA subscription, you will need to cancel them within your existing MOSP subscription and re-purchase them within your EA subscription. After doing so, you can submit a credit request for a refund for the potential month of overlapping coverage between the Marketplace service subscriptions - create a support ticket here.

Related questions and answers

  • Get answers to your technical questions in Microsoft Q&A, a community support channel where you can learn, connect, and exchange ideas with community experts, Microsoft engineers, and other customers. In addition, the robust search tool within Microsoft Q&A ingests answers from a variety of sources, making it a valuable self-help resource to meet your learning needs.

    • Technical support benefits may be available even if you don’t have a support plan. If you are a member of certain programs like MPN, MSDN or BizSpark, you may be eligible for limited Azure Support benefits from those Programs. Please refer to your service terms and conditions to understand your support options and benefits.
    • Your Azure subscription includes access to subscription management support, e.g. billing, quota adjustment, account transfer, at no additional cost. You can get started with your request in the Azure Portal. In addition, Microsoft Azure subscriptions include access to the Azure Status Dashboard and the Microsoft Q&A to help you troubleshoot issues.
  • We have designed our Azure Support plans to meet different business needs. Paid support plans provide access to Technical Support for break-fix issues on a 24x7 basis. Higher tiers of support plans offer faster initial response times and access to Advisory support, Configuration Optimization Reviews, and other benefits. More information about the existing support plans can be found at the Azure Support Plans page.

  • Azure support plans are customer support plans. Benefits in these plans are not transferrable to your customers.

  • Currently, the NV virtual machine promo will be available for on-demand deployment until 31 October 2020. The promo virtual machines deployed before that will continue to run. These virtual machines will be available for new deployments after the promo end date, but the promo pricing will no longer be in place. The promo end dates for NC and H series promo are not yet determined.

  • A brokered connection is defined as one of the following:

    1. An AMQP connection from a client into a Service Bus topic, subscription, queue, or event hub.
    2. An HTTP call to receive a message from a Service Bus topic or queue that has a receive timeout value greater than zero.

    Microsoft charges for the peak number of concurrent brokered connections that exceed the included quantity (1,000 in the standard and premium tier). Peaks are measured on an hourly basis, prorated by dividing by 730 hours in a month, and added up over the monthly billing period. The included quantity (1,000 brokered connections per month) is applied at the end of the billing period against the sum of the prorated hourly peaks.

    Examples:

    1. 5,000 clients connect via a single AMQP connection each, and receive commands from a Service Bus topic and send events to queues. If all clients connect for 12 hours every day, you will see the following connection charges (in addition to any other Service Bus charges)—5,000 connections * 12 hours * 30.5 days / 730 = 2,500 brokered connections. After the monthly allowance of 1,000 brokered connections, you would be charged for 1,500 brokered connections.
    2. 5,000 clients receive messages from a Service Bus queue via HTTP, specifying a non-zero timeout. If all devices connect for 12 hours every day, you will see the following connection charges (in addition to any other Service Bus charges)—5,000 HTTP receive connections * 12 hours per day * 30.5 days / 730 hours = 2,500 brokered connections.
  • QnA Maker helps you create a bot that conversationally answers questions covered in your documentation, like an FAQ page. Learn more about how QnA Maker works