Skip to content

Commit 16ea878

Browse files
committed
updated RP info
1 parent 6e183f0 commit 16ea878

File tree

1 file changed

+4
-37
lines changed

1 file changed

+4
-37
lines changed

articles/lighthouse/how-to/publish-managed-services-offers.md

Lines changed: 4 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to publish a managed service offer that onboards customer
44
author: JnHs
55
ms.author: jenhayes
66
ms.service: lighthouse
7-
ms.date: 10/17/2019
7+
ms.date: 11/08/2019
88
ms.topic: overview
99
manager: carmonm
1010
---
@@ -138,45 +138,12 @@ Once you've completed all of the sections, your next step is to publish the offe
138138

139139
## The customer onboarding process
140140

141-
When a customer adds your offer, they will be able to [delegate one or more specific subscriptions or resource groups](view-manage-service-providers.md#delegate-resources) which will then be onboarded for Azure delegated resource management. If a customer has accepted an offer but has not yet delegated any resources, they'll see a note at the top of the **Provider offers** section of the [**Service providers**](view-manage-service-providers.md) page in the Azure portal. If a user in the customer's tenant is unable to perform this delegation, it's probably because they don't have the Owner role for the subscription. To find users who can delegate the subscription, the user can select the subscription in the Azure portal, open **Access control (IAM)**, and [view all users with the Owner role](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal#view-roles-and-permissions).
141+
When a customer adds your offer, they will be able to [delegate one or more specific subscriptions or resource groups](view-manage-service-providers.md#delegate-resources) which will then be onboarded for Azure delegated resource management. If a customer has accepted an offer but has not yet delegated any resources, they'll see a note at the top of the **Provider offers** section of the [**Service providers**](view-manage-service-providers.md) page in the Azure portal. After the customer delegates a subscription (or one or more resource groups within a subscription), the **Microsoft.ManagedServices** resource provider will be registered for that subscription.
142142

143-
Before a subscription (or resource groups within a subscription) can be onboarded, the subscription must be authorized for onboarding by manually registering the **Microsoft.ManagedServices** resource provider. A user in the customer's tenant with the Contributor or Owner role can do this by following the steps outlined in [Azure resource providers and types](../../azure-resource-manager/resource-manager-supported-services.md).
144-
145-
The customer can then confirm that the subscription is ready for onboarding in one of the following ways.
146-
147-
### Azure portal
148-
149-
1. In the Azure portal, select the subscription.
150-
1. Select **Resource providers**.
151-
1. Confirm that **Microsoft.ManagedServices** shows as **Registered**.
152-
153-
### PowerShell
154-
155-
```azurepowershell-interactive
156-
# Log in first with Connect-AzAccount if you're not using Cloud Shell
157-
158-
Set-AzContext -Subscription <subscriptionId>
159-
Get-AzResourceProvider -ProviderNameSpace 'Microsoft.ManagedServices'
160-
```
143+
> [!IMPORTANT]
144+
> Delegation must be done by a non-guest account in the customer’s tenant which has the [Owner built-in role](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#owner) for the subscription being onboarded (or which contains the resource groups that are being onboarded). To see all users who can delegate the subscription, a user in the customer's tenant can select the subscription in the Azure portal, open **Access control (IAM)**, and [view all users with the Owner role](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal#view-roles-and-permissions).
161145
162-
This should return results similar to the following:
163146

164-
```output
165-
ProviderNamespace : Microsoft.ManagedServices
166-
RegistrationState : Registered
167-
ResourceTypes : {registrationDefinitions}
168-
Locations : {}
169-
170-
ProviderNamespace : Microsoft.ManagedServices
171-
RegistrationState : Registered
172-
ResourceTypes : {registrationAssignments}
173-
Locations : {}
174-
175-
ProviderNamespace : Microsoft.ManagedServices
176-
RegistrationState : Registered
177-
ResourceTypes : {operations}
178-
Locations : {}
179-
```
180147

181148
### Azure CLI
182149

0 commit comments

Comments
 (0)