Skip to content

Commit dda02b5

Browse files
authored
Apply pencil edit for blocking issue from PR review
1 parent 66bd719 commit dda02b5

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,10 @@ ms.service: azure-communication-services
1818

1919
In many applications end-users may want to store their Call Recording files long-term. Some of the common scenarios are compliance, quality assurance, assessment, post call analysis, training, and coaching. Now with the BYOS (bring your own storage) being available, end-users will have an option to store their files long term and manage the files in a way they need. The end user will be responsible for legal regulations about storing the data. BYOS simplifies downloading of the files from Azure Communication Services (ACS) and minimizes the number of support request if customer was unable to download recording in 48 hours. Data will be transferred securely from Microsoft Azure blob storage to a customer Azure blob storage.
2020
Here are a few examples:
21-
Contact Center Recording
22-
Compliance Recording Scenario
23-
Healthcare Virtual Visits Scenario
24-
Conference/meeting recordings and so on
21+
- Contact Center Recording
22+
- Compliance Recording Scenario
23+
- Healthcare Virtual Visits Scenario
24+
- Conference/meeting recordings and so on
2525

2626
BYOS can be easily integrated into any application regardless of the programming language. When creating a call recording resource in Azure Portal, enable the BYOS option and provide the sas-url to the storage. This simple experience allows developers to meet their needs, scale, and avoid investing time and resources into designing and maintaining a custom solution.
2727

0 commit comments

Comments
 (0)