RBAC settings aren't migrated

Author: spelluru

articles/service-bus-messaging/service-bus-migrate-standard-premium.md

@@ -2,7 +2,7 @@
 title: Migrate Azure Service Bus namespaces - standard to premium
 description: Guide to allow migration of existing Azure Service Bus standard namespaces to premium
 ms.topic: article
-ms.date: 03/09/2022
+ms.date: 06/27/2022
 ---
 
 # Migrate existing Azure Service Bus standard namespaces to the premium tier
@@ -21,6 +21,7 @@ Some of the points to note:
 - All **entities** in the standard namespace are **copied** to the premium namespace during the migration process.
 - Migration supports **1,000 entities per messaging unit** on the premium tier. To identify how many messaging units you need, start with the number of entities that you have on your current standard namespace.
 - You can't directly migrate from **basic tier** to **premium tier**, but you can do so indirectly by migrating from basic to standard first and then from the standard to premium in the next step.
+- The role-based access control (RBAC) settings are not migrated, so you will need to add them manually after the migration. 
 
 ## Migration steps
 
@@ -140,6 +141,9 @@ Here is a list of features not supported by Premium and their mitigation -
 
    If your ARM template sets 'enablePartitioning' to 'true' for a specific Queue or Topic, then it will be ignored by the broker.
 
+### RBAC settings
+The role-based access control (RBAC) settings on the namespace aren't migrated to the premium namespace. You'll need to add them manually after the migration. 
+
 ## FAQs
 
 ### What happens when the migration is committed?