updates from internal review

Author: rahulva-msft

articles/communication-services/concepts/call-automation/call-recording/bring-your-own-storage.md

@@ -27,7 +27,7 @@ Bring your own Azure storage uses [Azure Managed Identities](/entra/identity/man
 ## Known issues
 
 - Azure Communication Services will also store your files in a built-in storage for 24 hours even if the exporting is successful.
-- Randomly, recording files are duplicated during the exporting process. Make sure you delete the duplicated file to avoid extra storage costs in your storage account.
+- For Pause on Start Recording the meta data file would have an incorrect pause duration in relation to the recording file.
 
 
 ## Next steps

articles/communication-services/quickstarts/call-automation/call-recording/bring-your-own-storage.md

@@ -14,12 +14,8 @@ ms.custom: mode-api, devx-track-extended-java
 ---
 # Call recording: Bring your own Azure storage quickstart
 
-[!INCLUDE [Private Preview](../../../includes/private-preview-include-section.md)]
-
 This quickstart gets you started with Bring your own Azure storage for Call Recording. To start using Bring your own Azure Storage functionality, make sure you're familiar with the [Call Recording APIs](../../voice-video-calling/get-started-call-recording.md).
 
-You need to be part of the Azure Communication Services TAP program. It's likely that you’re already part of this program, and if you aren't, sign-up using https://aka.ms/acs-tap-invite. Bring your own Azure Storage uses Managed Identities, to access to this functionality for Call Recording, submit your Azure Communication Services Resource IDs by filling this - [Registration form](https://forms.office.com/r/njact5SiVJ). You need to fill the form every time you need a new resource ID allow-listed.
-
 ## Pre-requisite: Setting up Managed Identity and RBAC role assignments
 
 ### 1. Enable system assigned managed identity for Azure Communication Services
@@ -77,7 +73,7 @@ Refer to this example of the event schema.
     "topic": "string", // /subscriptions/{subscription-id}/resourceGroups/{group-name}/providers/Microsoft.Communication/communicationServices/{communication-services-resource-name}
     "subject": "string", // /recording/call/{call-id}/serverCallId/{serverCallId}
     "data": {
-        "storageType": "string", // acsstorage, blobstorage etc.
+        "storageType": "string", // AzureBlob etc.
         "recordingId": "string", // unique id for recording
         "recordingStorageInfo": {
             "recordingChunks": [
@@ -106,12 +102,12 @@ Refer to this example of the event schema.
 Recordings are stored in the following format as shown in the diagram.
         /YYYYMMDD/
             callId/
-            8+ recordingId(guid)/
+                first_8_of_recordingId + '-' + unique guid)/   
                                 0-acsmetadata.documentId.json
-                                0- audiomp3.documentId.mp3
+                                0-audiomp3.documentId.mp3
                                 1-acsmetadata.documentId.json
                                 1-audiomp3.documentId.mp3
-                                
+
 ![Diagram showing a Call Recording Folder structure](../media/call-recording-folder.png)
 
 ## Next steps

articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-csharp.md

@@ -78,7 +78,8 @@ Response<RecordingStateResult> response = await callAutomationClient.GetCallReco
 .StartAsync(recordingOptions);
 ```
 ## 2.2. Start recording session with Pause mode enabled using 'StartAsync' API
-
+> [!NOTE]
+> **Recordings will need to be resumed for recording file to be generated.**
 ```csharp
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<ServerCallId>")) 
 {

articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-java.md

@@ -81,7 +81,8 @@ Start Recording session with your own Azure Blob Storage to store the recording
 ```
 
 ### 2.2. Start recording session with Pause mode enabled using 'StartAsync' API
-
+> [!NOTE]
+> **Recordings will need to be resumed for recording file to be generated.**
 ```java
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<serverCallId>"))
                     .setRecordingChannel(RecordingChannel.UNMIXED)

articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-javascript.md

@@ -85,7 +85,8 @@ var options: StartRecordingOptions = {
 var response = await callAutomationClient.getCallRecording().start(options);
 ```
 ## 2.2. Start recording session with Pause mode enabled using 'StartAsync' API
-
+> [!NOTE]
+> **Recordings will need to be resumed for recording file to be generated.**
 ```javascript
 var locator: CallLocator = { id: "<ServerCallId>", kind: "serverCallLocator" };
 

articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-python.md

@@ -71,6 +71,8 @@ response = call_automation_client.start_recording(call_locator=ServerCallLocator
                    recording_storage = AzureBlobContainerRecordingStorage(container_url="<YOUR_STORAGE_CONTAINER_URL>"))
 ```
 ## 2.2. Start recording session with Pause mode enabled using 'StartAsync' API
+> [!NOTE]
+> **Recordings will need to be resumed for recording file to be generated.**
 
 ```python
 response = call_automation_client.start_recording(call_locator=ServerCallLocator(server_call_id),