Skip to content

Commit 22ccc9e

Browse files
authored
Merge pull request #232404 from JnHs/jh-lh-msfresh23
refresh topics
2 parents 53fbe77 + 8c1e2c6 commit 22ccc9e

File tree

3 files changed

+24
-22
lines changed

3 files changed

+24
-22
lines changed

articles/lighthouse/concepts/managed-services-offers.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Managed Service offers in Azure Marketplace
33
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
55
ms.topic: conceptual
66
---
77

@@ -13,7 +13,7 @@ This article describes the **Managed Service** offer type in [Azure Marketplace]
1313

1414
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.
1515

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).
1717

1818
> [!NOTE]
1919
> 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
2222

2323
Each Managed Service offer includes one or more plans. Plans can be either private or public.
2424

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).
2626

2727
> [!NOTE]
2828
> 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
3232
If appropriate, you can include both public and private plans in the same offer.
3333

3434
> [!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).
3636
3737
## Publish Managed Service offers
3838

@@ -41,4 +41,5 @@ To learn how to publish a Managed Service offer, see [Publish a Managed Service
4141
## Next steps
4242

4343
- 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).
4445
- [Publish Managed Service offers](../how-to/publish-managed-services-offers.md) to Azure Marketplace.

articles/lighthouse/how-to/partner-earned-credit.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,13 @@ ms.topic: how-to
77

88
# Link your partner ID to track your impact on delegated resources
99

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).
1111

1212
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.
1313

1414
## Associate your partner ID when you onboard new customers
1515

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.
1717

1818
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.
1919

@@ -33,7 +33,7 @@ Once the account has been [linked to your Associated Partner ID](../../cost-mana
3333

3434
## Confirm partner earned credit
3535

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.
3737

3838
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).
3939

@@ -43,4 +43,4 @@ You can also use the [Partner Center SDK](/partner-center/develop/get-invoice-un
4343

4444
- Learn more about the [Microsoft Cloud Partner Program](/partner-center/mpn-overview).
4545
- 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

Comments
 (0)