Skip to content

Commit 8726da3

Browse files
Merge pull request #247517 from EldertGrootenboer/EldertGrootenboer-patch-1
Update transfer-subscription.md
2 parents b0a70ef + 2b47b36 commit 8726da3

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/role-based-access-control/transfer-subscription.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,7 @@ Several Azure resources have a dependency on a subscription or a directory. Depe
8484
| App registrations | Yes | Yes | | |
8585
| Microsoft Dev Box | Yes | No | | You cannot transfer a dev box and its associated resources to a different directory. Once a subscription moves to another tenant, you will not be able to perform any actions on your dev box |
8686
| Azure Deployment Environments | Yes | No | | You cannot transfer an environment and its associated resources to a different directory. Once a subscription moves to another tenant, you will not be able to perform any actions on your environment |
87+
| Azure Service Bus | Yes | Yes | |You must delete, re-create, and attach the managed identities to the appropriate resource. You must re-create the role assignments. |
8788

8889
> [!WARNING]
8990
> If you are using encryption at rest for a resource, such as a storage account or SQL database, that has a dependency on a key vault that is being transferred, it can lead to an unrecoverable scenario. If you have this situation, you should take steps to use a different key vault or temporarily disable customer-managed keys to avoid this unrecoverable scenario.

0 commit comments

Comments
 (0)