remove byos reference from public docs

Author: sarkar-rajarshi

articles/communication-services/concepts/voice-video-calling/call-recording.md

@@ -63,15 +63,6 @@ A `recordingId` is returned when recording is started, which is then used for fo
 | Stop Recording        | `recordingId` | Stops recording, and initiates final media processing for file download. | 
 
 
-## Bring your own storage
-
-[!INCLUDE [Private Preview](../../includes/private-preview-include-section.md)]
-
-Call Recording APIs can be used to export recordings to your Azure Blob Storage Container as well. While starting recording for a call, simply specify the container path where the recording needs to be exported. Upon recording completion, Azure Communication Services will automatically fetch and upload your recording to your storage.
-
-
-![Diagram showing a call recording being automatically exported to storage container](./media/call-recording-byos-flow-zoomed.png)
-
 ## Event Grid notifications
 Call Recording use [Azure Event Grid](../../../event-grid/event-schema-communication-services.md) to provide you with notifications related to media and metadata.
 

articles/communication-services/quickstarts/voice-video-calling/get-started-call-recording.md

@@ -26,47 +26,6 @@ This quickstart gets you started with Call Recording for voice and video calls.
 [!INCLUDE [Test Call Recording with Java](./includes/call-recording-samples/call-recording-java.md)]
 ::: zone-end
 
-## Call Recording: Bring your own storage
-
-[!INCLUDE [Public Preview](../../includes/private-preview-include-section.md)]
-
-### Pre-requisite: Setting up Managed Identity and RBAC Role Assignments
-
-#### 1.1 Enable System Assigned Managed Identity for Azure Communication Services
-
-![Diagram showing a communication service resource with managed identity disabled](../media/call-recording-byos-pre-requisite-1.png)
-
-1. Open your Azure Communication Services resource. Navigate to *Identity* on the left.
-2. System Assigned Managed Identity is disabled by default. Enable it and click of *Save*
-3. Once completed, you'll be able to see the Object principal ID of the newly created identity (shown below)
-![Diagram showing a communication service resource with managed identity enabled](../media/call-recording-byos-pre-requisite-2.png)
-4. Now that identity has been successfully created, click on *Azure role assignments* to start adding role assignments.
-
-#### 1.2 Add Role Assignment
-
-1. Click on *"Add role assignment"*
-![Diagram showing a communication service resource managed identity adding role assignment](../media/call-recording-byos-pre-requisite-3.png)
-
-2. On the *"Add role assignment"* panel, select the following values
-    1. Scope: **Storage**
-    2. Subscription: **Choose your subscription**
-    3. Resource: **Choose your storage account**
-    4. Role: **Azure Communication Services needs *"Storage Blob Data Contributor"* to be able to write to your storage account.**
-![Diagram showing a communication service resource managed identity adding role assignment details](../media/call-recording-byos-pre-requisite-4.png)
-
-3. Click on *"Save"*.
-4. Once completed, you will see the newly added role assignment in the *"Azure role assignment"* window (shown below).
-![Diagram showing a communication service resource managed identity role assignment success](../media/call-recording-byos-pre-requisite-5.png)
-
-
-::: zone pivot="programming-language-csharp"
-[!INCLUDE [Test Call Recording BYOS with C#](./includes/call-recording-samples/private-preview-call-recording-byos-csharp.md)]
-::: zone-end
-
-::: zone pivot="programming-language-java"
-[!INCLUDE [Test Call Recording BYOS with Java](./includes/call-recording-samples/private-preview-call-recording-byos-java.md)]
-::: zone-end
-
 
 ## Clean up resources