You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/lighthouse/concepts/managed-services-offers.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Managed Service offers in Azure Marketplace
3
3
description: Offer your Azure Lighthouse management services to customers through Managed Services offers in Azure Marketplace.
4
-
ms.date: 06/09/2022
4
+
ms.date: 03/28/2023
5
5
ms.topic: conceptual
6
6
---
7
7
@@ -13,7 +13,7 @@ This article describes the **Managed Service** offer type in [Azure Marketplace]
13
13
14
14
Managed Service offers streamline the process of onboarding customers to Azure Lighthouse. When a customer purchases an offer in Azure Marketplace, they'll be able to specify which subscriptions and/or resource groups should be onboarded.
15
15
16
-
For each offer, you define the access that users in your organization will have to work on resources in the customer tenant. This is done through a manifest that specifies the Azure Active Directory (Azure AD) users, groups, and service principals that will have access to customer resources, along with [roles](tenants-users-roles.md#role-support-for-azure-lighthouse) that define their level of access.
16
+
For each offer, you define the access that users in your organization will have to work on resources in the customer tenant. This is done through a manifest that specifies the Azure Active Directory (Azure AD) users, groups, and service principals that will have access to customer resources, along with [roles that define their level of access](tenants-users-roles.md#role-support-for-azure-lighthouse).
17
17
18
18
> [!NOTE]
19
19
> Managed Service offers may not be available in Azure Government and other national clouds.
@@ -22,7 +22,7 @@ For each offer, you define the access that users in your organization will have
22
22
23
23
Each Managed Service offer includes one or more plans. Plans can be either private or public.
24
24
25
-
If you want to limit your offer to specific customers, you can publish a private plan. When you do so, the plan can only be purchased for the specific subscription IDs that you provide. For more info, see [Private plans](../../marketplace/private-plans.md).
25
+
If you want to limit your offer to specific customers, you can publish a private plan. When you do so, the plan can only be purchased for the specific subscription IDs that you provide. For more info, see [Private plans](/partner-center/marketplace/private-plans).
26
26
27
27
> [!NOTE]
28
28
> Private plans are not supported with subscriptions established through a reseller of the Cloud Solution Provider (CSP) program.
@@ -32,7 +32,7 @@ Public plans let you promote your services to new customers. These are usually m
32
32
If appropriate, you can include both public and private plans in the same offer.
33
33
34
34
> [!IMPORTANT]
35
-
> Once a plan has been published as public, you can't change it to private. To control which customers can accept your offer and delegate resources, use a private plan. With a public plan, you can't restrict availability to certain customers or even to a certain number of customers (although you can stop selling the plan completely if you choose to do so). You can [remove access to a delegation](../how-to/remove-delegation.md) after a customer accepts an offer only if you included an **Authorization** with the **Role Definition** set to [Managed Services Registration Assignment Delete Role](../../role-based-access-control/built-in-roles.md#managed-services-registration-assignment-delete-role) when you published the offer. You can also reach out to the customer and ask them to [remove your access](../how-to/view-manage-service-providers.md#remove-service-provider-offers).
35
+
> Once a plan has been published as public, you can't change it to private. To control which customers can accept your offer and delegate resources, use a private plan. With a public plan, you can't restrict availability to certain customers or even to a certain number of customers (although you can stop selling the plan completely if you choose to do so). After a customer accepts an offer, you can [remove access to a delegation](../how-to/remove-delegation.md) only if you included an **Authorization** with the **Role Definition** set to [Managed Services Registration Assignment Delete Role](../../role-based-access-control/built-in-roles.md#managed-services-registration-assignment-delete-role) when you published the offer. You can also reach out to the customer and ask them to [remove your access](../how-to/view-manage-service-providers.md#remove-service-provider-offers).
36
36
37
37
## Publish Managed Service offers
38
38
@@ -41,4 +41,5 @@ To learn how to publish a Managed Service offer, see [Publish a Managed Service
41
41
## Next steps
42
42
43
43
- Learn about Azure Lighthouse [architecture](architecture.md) and [cross-tenant management experiences](cross-tenant-management-experience.md).
44
+
- Learn about the [commercial marketplace](/partner-center/marketplace/overview).
44
45
-[Publish Managed Service offers](../how-to/publish-managed-services-offers.md) to Azure Marketplace.
Copy file name to clipboardExpand all lines: articles/lighthouse/how-to/partner-earned-credit.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ ms.topic: how-to
7
7
8
8
# Link your partner ID to track your impact on delegated resources
9
9
10
-
If you're a member of the [Microsoft Cloud Partner Program](https://partner.microsoft.com/), you can link your partner ID with the credentials used to manage delegated customer resources. This link allows Microsoft to identify and recognize partners who drive Azure customer success. It also allows [CSP (Cloud Solution Provider)](/partner-center/csp-overview) partners to receive [partner earned credit for managed services (PEC)](/partner-center/partner-earned-credit) for customers who have [signed the Microsoft Customer Agreement (MCA)](/partner-center/confirm-customer-agreement) and are [under the Azure plan](/partner-center/azure-plan-get-started).
10
+
If you're a member of the [Microsoft Cloud Partner Program](https://partner.microsoft.com/), you can link your partner ID with the credentials used to manage delegated customer resources. This link allows Microsoft to identify and recognize partners who drive Azure customer success. It also allows [CSP (Cloud Solution Provider)](/partner-center/csp-overview) partners to receive [partner earned credit (PEC)](/partner-center/partner-earned-credit) for customers who have [signed the Microsoft Customer Agreement (MCA)](/partner-center/confirm-customer-agreement) and are [under the Azure plan](/partner-center/azure-plan-get-started).
11
11
12
12
To earn recognition for Azure Lighthouse activities, you'll need to [link your partner ID](../../cost-management-billing/manage/link-partner-id.md) with at least one user account in your managing tenant, and ensure that the linked account has access to each of your onboarded subscriptions.
13
13
14
14
## Associate your partner ID when you onboard new customers
15
15
16
-
Use the following process to link your partner ID (and enable partner earned credit, if applicable). You'll need to know your [partner ID](/partner-center/partner-center-account-setup#locate-your-partner-id) to complete these steps. Be sure to use the **Associated Partner ID** shown on your partner profile.
16
+
Use the following process to link your partner ID (and enable partner earned credit, if applicable). You'll need to know your [partner ID](/partner-center/partner-center-account-setup#locate-your-partnerd) to complete these steps. Be sure to use the **Associated Partner ID** shown on your partner profile.
17
17
18
18
For simplicity, we recommend creating a service principal account in your tenant, linking it to your **Associated Partner ID**, then granting it an [Azure built-in role that is eligible for PEC](/partner-center/azure-roles-perms-pec) to every customer that you onboard.
19
19
@@ -33,7 +33,7 @@ Once the account has been [linked to your Associated Partner ID](../../cost-mana
33
33
34
34
## Confirm partner earned credit
35
35
36
-
You can [view PEC details in the Azure portal](/partner-center/partner-earned-credit-explanation#azure-cost-management) and confirm which costs have received the benefit of PEC. Remember that PEC only applies to CSP customers who have signed the MCA and are under the Azure plan.
36
+
You can [view PEC details in the Azure portal](/partner-center/partner-earned-credit-explanation#use-acm-to-view-your-partner-earned-credit) and confirm which costs have received the benefit of PEC. Remember that PEC only applies to CSP customers who have signed the MCA and are under the Azure plan.
37
37
38
38
If you have followed the steps above, and do not see the expected association, [open a support request in the Azure portal](../../azure-portal/supportability/how-to-create-azure-support-request.md).
39
39
@@ -43,4 +43,4 @@ You can also use the [Partner Center SDK](/partner-center/develop/get-invoice-un
43
43
44
44
- Learn more about the [Microsoft Cloud Partner Program](/partner-center/mpn-overview).
45
45
- Learn [how PEC is calculated and paid](/partner-center/partner-earned-credit-explanation).
46
-
-[Onboard customers](onboard-customer.md) to Azure Lighthouse.
46
+
-[Onboard customers](onboard-customer.md) to Azure Lighthouse.
0 commit comments