removed overview

Author: sushantjrao

articles/operator-nexus/concepts-cross-subscription-deployments-required-rbac-for-network-fabric.md

@@ -9,27 +9,25 @@ ms.date: 09/17/2024
 ms.custom: template-concept
 ---
 
-# Managing Azure Network Fabric Resources Across Subscriptions
-
-## Overview
+# Managing Azure Network Fabric resources across subscriptions
 
 This document outlines the requirements and behaviors associated with managing Nexus Network Fabric (NNF) resources in Azure when dealing with multiple subscriptions. It describes various scenarios involving different levels of access permissions that can affect operations across subscriptions. This document also covers the linked access check implementation, which ensures that proper permissions and access controls are enforced when managing Network Fabric (NNF) resources across multiple subscriptions, verifying that the required cross-subscription links have the necessary authorizations in place.
 
 ## Scenarios
 
-### Limited access in Subscription A
+### Limited access in subscription A
 
 In this scenario, the user has access to two subscriptions: **Subscription A** and **Subscription B**. In **Subscription A**, the user has only `read` access to the Network Fabric (NNF) resources.
 
 **Outcome:** When the user tries to create or manage any NNF resource in **Subscription B** by referencing the NNF resource from **Subscription A**, the operation fails with a `LinkedAuthorizationFailed` error. This failure occurs because the user does not have the necessary `Join` access to the NNF resource.
 
-### Sufficient Access in Both Subscriptions
+### Sufficient access in both subscriptions
 
 In this scenario, the user has access to both **Subscription A** and **Subscription B**, with either `Contributor` or `Owner` permissions in both subscriptions.
 
 **Outcome**: When the user tries to create or manage Network Fabric (NNF) resources in **Subscription B** by referencing NNF resources in **Subscription A**, the operation succeeds. This confirms that sufficient permissions enable successful resource management across subscriptions.
 
-### No Access to Subscription A
+### No access to subscription A
 
 In this scenario, the user has no access to **Subscription A**, where the Network Fabric (NNF) resources are deployed, but has Contributor or Owner rights in **Subscription B**.
 
@@ -39,7 +37,7 @@ When the user tries to create or manage NNF resources in **Subscription B** by r
 >[!NOTE]
 >Network Fabric cannot be created in a different subscription than the referenced Network Fabric Controller (NFC).
 
-## Permissions Overview
+## Permissions overview
 
 To effectively manage NNF resources across Azure subscriptions, users must have the appropriate permissions. The following permissions are essential:
 
@@ -53,22 +51,22 @@ To effectively manage NNF resources across Azure subscriptions, users must have
 
 - **Join access:** Users must have Join access to the specific NNF resources they wish to reference. For example, when a user tries to create an L2 or L3 isolation domain in **Subscription B** while referencing an NNF resource in **Subscription A**, the user must have Join access on the NNF resource.
 
-## Resource Management Considerations
+## Resource management considerations
 
-### Resource Creation
+### Resource creation
 
 - Ensure that users have the necessary subscription-level permissions before attempting to create NNF resources.
 
 - When referencing resources from another subscription, confirm that the user has both read access to that subscription and Join access to the specific NNF resource.
 
-### Resource Configuration
+### Resource configuration
 
 - Users with 'Contributor` or `Owner` access can configure NNF resources. However, they must have the appropriate permissions for each specific configuration action.
 
-### Resource Deletion
+### Resource deletion
 
 - Deleting NNF resources typically requires `Contributor`, `Owner` or `Delete` access on the resource. Users should be aware of any dependencies that may prevent deletion.
 
-### Cross-Subscription Management
+### Cross-Subscription management
 
 - When managing NNF resources across multiple subscriptions, it’s crucial to maintain a clear understanding of the permissions structure to avoid `AuthorizationFailed` and `LinkedAuthorizationFailed` errors.