Skip to content

Commit 4c7c230

Browse files
authored
Merge pull request #111704 from emuench/patch-6
Terminology updates from SME
2 parents ca58527 + a9669a9 commit 4c7c230

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/marketplace/partner-center-portal/azure-vm-create-offer.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -291,7 +291,7 @@ Select **Save draft** before proceeding to the next section, Plan overview.
291291

292292
## Plan overview
293293

294-
You can provide different plan options within the same offer in Partner Center. These plans were previously referred to as SKUs. An offer requires at least one plan, which can differ in terms of monetization audience, Azure clouds, features, or VM images.
294+
You can provide different plan options within the same offer in Partner Center. These plans were previously referred to as SKUs. An offer requires at least one plan, which can differ in terms of monetization audience, Azure regions, features, or VM images.
295295

296296
After you create your plans, the **Plan overview** tab shows:
297297

@@ -321,7 +321,7 @@ Select **Create**.
321321

322322
### Plan setup
323323

324-
Set the high-level configuration for the type of plan, whether it reuses technical configuration from another plan, and in what clouds the plan should be available. Your selections here determine which fields are displayed on other tabs for the same plan.
324+
Set the high-level configuration for the type of plan, whether it reuses technical configuration from another plan, and in which Azure regions the plan should be available. Your selections here determine which fields are displayed on other tabs for the same plan.
325325

326326
#### Reuse technical configuration
327327

@@ -330,24 +330,24 @@ If you have more than one plan of the same type, and the packages are identical
330330
> [!NOTE]
331331
> When you reuse the technical configuration from another plan, the entire **Technical configuration** tab disappears from this plan. The Technical configuration details from the other plan, including any updates you make in the future, will be used for this plan as well. This setting can't be changed after this plan is published.
332332
333-
#### Cloud availability
333+
#### Azure regions
334334

335-
Your plan must be made available in at least one cloud.
335+
Your plan must be made available in at least one Azure region.
336336

337-
Select the **Azure Global** option to make your plan available to customers in all public Azure regions that have commercial marketplace integration. For details, see [Geographic availability and currency support](https://aka.ms/AzureGovCurrencies).
337+
Select the **Azure Global** option to make your plan available to customers in all public Azure regions that have commercial marketplace integration. For details, see [Geographic availability and currency support](https://docs.microsoft.com/azure/marketplace/marketplace-geo-availability-currencies).
338338

339-
Select the **Azure Government Cloud** option to make your plan available in the [Azure Government Cloud](https://aka.ms/WhatIsAzureGovernment). this is a government-community cloud with controlled access for customers from U.S. federal, state, local or tribal agencies as well as partners eligible to serve these entities. As the publisher, you're responsible for any compliance controls, security measures, and best practices to serve this cloud community. Azure Government uses physically isolated data centers and networks (located in the U.S. only).
339+
Select the **Azure Government** option to make your plan available in the [Azure Government](https://docs.microsoft.com/azure/azure-government/documentation-government-welcome) region. This region provides controlled access for customers from U.S. federal, state, local, or tribal entities, as well as partners eligible to serve them. You, as the publisher, are responsible for any compliance controls, security measures, and best practices. Azure Government uses physically isolated data centers and networks (located in the U.S. only).
340340

341-
Before publishing to [Azure Government](https://aka.ms/azuregovpublish), test and validate your plan in the environment as certain endpoints may differ. To set up and test your plan, request a trial account from [Microsoft Azure Government trial](https://aka.ms/AzureGovernmentTrial).
341+
Before publishing to [Azure Government](https://docs.microsoft.com/azure/azure-government/documentation-government-manage-marketplace-partners), test and validate your plan in the environment as certain endpoints may differ. To set up and test your plan, request a trial account from [Microsoft Azure Government trial](https://azure.microsoft.com/global-infrastructure/government/request/).
342342

343343
> [!NOTE]
344-
> After your plan is published and available in a specific cloud, you can't remove that cloud.
344+
> After your plan is published and available in a specific Azure region, you can't remove that region.
345345
346-
#### Azure Government Cloud certifications
346+
#### Azure Government certifications
347347

348-
This option is only visible if **Azure Government Cloud** is selected under **Cloud availability**.
348+
This option is only visible if you select **Azure Government** under **Azure regions**.
349349

350-
Azure Government services handle data that is subject to certain government regulations and requirements. For example, FedRAMP, NIST 800.171 (DIB), ITAR, IRS 1075, DoD L4, and CJIS. To bring awareness to your certifications for these programs, you can provide up to 100 links that describe them. These can be either links to your listing on the program directly or links to descriptions of your compliance with them on your own websites. These links visible to Azure Government Cloud customers only.
350+
Azure Government services handle data that is subject to certain government regulations and requirements. For example, FedRAMP, NIST 800.171 (DIB), ITAR, IRS 1075, DoD L4, and CJIS. To bring awareness to your certifications for these programs, you can provide up to 100 links that describe them. These can be either links to your listing on the program directly or links to descriptions of your compliance with them on your own websites. These links visible to Azure Government customers only.
351351

352352
Select **Save draft** before continuing.
353353

@@ -379,7 +379,7 @@ On this tab, you'll configure the following:
379379

380380
#### Markets
381381

382-
Every plan must be available in at least one market. Select the check box for every market location where this plan should be available for purchase (users in these markets can still deploy the offer to all Azure regions for the clouds selected). The **Tax Remitted** button shows countries in which Microsoft remits sales and use tax on your behalf. Publishing to China is limited to plans that are either **Free** or **Bring your own license** (BYOL).
382+
Every plan must be available in at least one market. Select the check box for every market location where this plan should be available for purchase (users in these markets can still deploy the offer to all Azure regions selected in **[Plan setup](#plan-setup)**). The **Tax Remitted** button shows countries in which Microsoft remits sales and use tax on your behalf. Publishing to China is limited to plans that are either **Free** or **Bring your own license** (BYOL).
383383

384384
If you've already set prices for your plan in United States Dollars (USD) and add another market location, the price for the new market will be calculated according to current exchange rates. Always review the price for each market before publishing. Review prices using the **Export prices (xlsx)** link after saving your changes.
385385

0 commit comments

Comments
 (0)