Skip to content

Commit a596629

Browse files
authored
Merge pull request #199335 from dannyevers/69578-azure-managed
69578-azire-managed
2 parents 50f7cfb + 8bb29f0 commit a596629

File tree

2 files changed

+3
-7
lines changed

2 files changed

+3
-7
lines changed

articles/marketplace/plan-azure-app-managed-app.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: dannyevers
77
ms.service: marketplace
88
ms.subservice: partnercenter-marketplace-publisher
99
ms.topic: conceptual
10-
ms.date: 11/02/2021
10+
ms.date: 05/25/2022
1111
---
1212

1313
# Plan an Azure managed application for an Azure application offer
@@ -28,7 +28,7 @@ Use an Azure Application: Managed application plan when the following conditions
2828
| An Azure subscription | Managed applications must be deployed to a customer's subscription, but they can be managed by a third party. |
2929
| Billing and metering | The resources are provided in a customer's Azure subscription. VMs that use the pay-as-you-go payment model are transacted with the customer via Microsoft and billed via the customer's Azure subscription. <br><br> For bring-your-own-license VMs, Microsoft bills any infrastructure costs that are incurred in the customer subscription, but you transact software licensing fees with the customer directly. |
3030
| Azure-compatible virtual hard disk (VHD) | VMs must be built on Windows or Linux. For more information, see:<br> * [Create an Azure VM technical asset](./azure-vm-certification-faq.yml#address-a-vulnerability-or-an-exploit-in-a-vm-offer) (for Windows VHDs).<br> * [Linux distributions endorsed on Azure](../virtual-machines/linux/endorsed-distros.md) (for Linux VHDs). |
31-
| Customer usage attribution | All new Azure application offers must also include an [Azure partner customer usage attribution](azure-partner-customer-usage-attribution.md) GUID. For more information about customer usage attribution and how to enable it, see [Azure partner customer usage attribution](azure-partner-customer-usage-attribution.md). |
31+
| Customer usage attribution | For more information about customer usage attribution and how to enable it, see [Azure partner customer usage attribution](azure-partner-customer-usage-attribution.md). |
3232
| Deployment package | You'll need a deployment package that will let customers deploy your plan. If you create multiple plans that require the same technical configuration, you can use the same package. For details, see the next section: Deployment package. |
3333

3434
> [!NOTE]
@@ -70,8 +70,6 @@ Maximum file sizes supported are:
7070
- Up to 1 Gb in total compressed .zip archive size
7171
- Up to 1 Gb for any individual uncompressed file within the .zip archive
7272

73-
All new Azure application offers must also include an [Azure partner customer usage attribution](azure-partner-customer-usage-attribution.md) GUID.
74-
7573
## Azure regions
7674

7775
You can publish your plan to the Azure public region, Azure Government region, or both. Before publishing to [Azure Government](../azure-government/documentation-government-manage-marketplace-partners.md), 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/).

articles/marketplace/plan-azure-app-solution-template.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: dannyevers
77
ms.service: marketplace
88
ms.subservice: partnercenter-marketplace-publisher
99
ms.topic: conceptual
10-
ms.date: 11/11/2021
10+
ms.date: 05/25/2022
1111
---
1212

1313
# Plan a solution template for an Azure application offer
@@ -40,8 +40,6 @@ Maximum file sizes supported are:
4040
- Up to 1 Gb in total compressed .zip archive size
4141
- Up to 1 Gb for any individual uncompressed file within the .zip archive
4242

43-
All new Azure application offers must also include an [Azure partner customer usage attribution](azure-partner-customer-usage-attribution.md) GUID.
44-
4543
## Azure regions
4644

4745
You can publish your plan to the Azure public region, Azure Government region, or both. Before publishing to [Azure Government](../azure-government/documentation-government-manage-marketplace-partners.md), 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/).

0 commit comments

Comments
 (0)