Merge pull request #79800 from qianw211/ManagedApps1

reverting to original text before engineering release

Author: ShannonLeavitt

articles/marketplace/marketplace-managed-apps.md

@@ -28,48 +28,13 @@ Use the Azure app: managed app offer type when the following conditions are requ
 
 |Requirements |Details  |
 |---------|---------|
-|Deployed to a customer’s Azure subscription | Managed Apps must be deployed in the customer’s subscription and can be managed by a 3rd party | 
-|Billing and metering    |  The resources will be provisioned in the customer’s Azure subscription. Pay-as-you-go (PAYGO) virtual machines can be transacted with the customer via Microsoft, and billed by the following methods: <br> - via the customer’s Azure subscription (PAYGO), <br> - the infrastructure can be charged to the partner in which case the customer pays a monthly flat fee.        |
+|Deployed to a customer's Azure subscription | Managed Apps must be deployed in the customer’s subscription and can be managed by a third party. | 
+|Billing and metering    |  The resources will be provisioned in the customer’s Azure subscription. Pay-as-you-go (PAYGO) virtual machines will be transacted with the customer via Microsoft, billed via the customer’s Azure subscription (PAYGO). <br> In the case of bring-your-own-license, while Microsoft will bill infrastructure costs incurred in the customer subscription, you will transact your software licensing fees to the customer directly.        |
 |Azure-compatible virtual hard disk (VHD)    |   VMs must be built on Windows or Linux.<ul> <ul> <li>For more information about creating a Linux VHD, see [Linux distributions endorsed on Azure](https://docs.microsoft.com/azure/virtual-machines/linux/endorsed-distros).</li> <li>For more information about creating a Windows VHD, see [Create an Azure-compatible VHD](./cloud-partner-portal/virtual-machine/cpp-create-vhd.md).</li> </ul> |
 
 >[!NOTE]
 > Managed apps must be deployable through the Marketplace. If customer communication is a concern, then you should reach out to interested customers after you have enabled lead sharing.  
 
-## Infrastructure billing
-
-There are two options for infrastructure costs: Paid by customer or paid by partner. The default configuration is set to Customer.  When the configuration is switched to Partner, the publisher will be billed for the Azure resource consumption. In this scenario, the publisher sets a flat fee paid by the customer that includes the cost of infrastructure, IP, and services.
-
-The following resource types are eligible for publisher charging:
-
-* AppInsights
-* Azure functions
-* AzureRedisCache
-* Bandwidth
-* Batch
-* CDN
-* ClassicCompute
-* CognitiveServices
-* Compute
-* Databricks
-* DataFactory
-* DataLakeAnalytics
-* DataLakeStore
-* DocumentDB
-* HDInsight
-* KeyVault
-* Kubernetes
-* Kusto
-* Network
-* Power BI
-* PostgreSQL
-* Redis cache
-* Search
-* SoftwareLoadBalancer
-* SqlAzure
-* Storage
-* VMWareCS
-* Websites
-
 >[!Note]
 >Cloud Solution Providers (CSP) partner channel opt-in is now available.  Please see [Cloud Solution Providers](./cloud-solution-providers.md) for more information on marketing your offer through the Microsoft CSP partner channels.