Skip to content

Commit ca1dd70

Browse files
committed
more cleanup
1 parent f58d6e1 commit ca1dd70

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

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

Lines changed: 5 additions & 6 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: 11/08/2019
7+
ms.date: 11/11/2019
88
ms.topic: overview
99
manager: carmonm
1010
---
@@ -138,16 +138,15 @@ Once you've completed all of the sections, your next step is to publish the offe
138138

139139
## The customer onboarding process
140140

141-
After a customer adds your offer, they'll 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.
141+
After a customer adds your offer, they'll 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.
142142

143143
> [!IMPORTANT]
144144
> 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).
145145
146-
Note that currently, subscriptions (or resource groups within a subscription) can't be delegated if the subscription uses Azure Databricks. Similarly, if a subscription (or resource groups within a subscription) has been delegated, it currently will not be possible to create Databricks workspaces in that subscription.
147-
148-
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, and users in your tenant will be able to access the delegated resources according to the authorizations in your offer.
149-
146+
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, and users in your tenant will be able to access the delegated resources according to the authorizations in your offer.
150147

148+
> [!NOTE]
149+
> Currently, subscriptions (or resource groups within a subscription) can't be delegated if the subscription uses Azure Databricks. Similarly, if a subscription (or resource groups within a subscription) has already been delegated, it currently isn't possible to create Databricks workspaces in that subscription.
151150
152151
## Next steps
153152

0 commit comments

Comments
 (0)