Skip to content

Commit 7f10ada

Browse files
committed
update
1 parent 5b8fdf2 commit 7f10ada

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/communication-services/concepts/voice-video-calling/end-of-call-survey.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ Screenshare. However, each API value can be customized from a minimum of
107107

108108
- ***Note**: A question’s indicated cutoff value in the API is the threshold that Microsoft uses when analyzing your survey data. When you customize the cutoff value or Input Range, Microsoft analyzes your survey data according to your customization.
109109

110-
## Store and view survey data:
110+
<!-- ## Store and view survey data:
111111
112112
> [!IMPORTANT]
113113
> You must enable a Diagnostic Setting in Azure Monitor to send the log data of your surveys to a Log Analytics workspace, Event Hubs, or an Azure storage account to receive and analyze your survey data. If you do not send survey data to one of these options your survey data will not be stored and will be lost. To enable these logs for your Communications Services, see: **[Enable logging in Diagnostic Settings](../analytics/enable-logging.md)**
@@ -118,7 +118,7 @@ You can only view your survey data if you have enabled a Diagnostic Setting to c
118118
119119
- Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
120120
121-
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../../articles/azure-monitor/logs/get-started-queries.md)
121+
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../../articles/azure-monitor/logs/get-started-queries.md) -->
122122

123123

124124

articles/communication-services/tutorials/end-of-call-survey-tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ API will return the error messages when data validation failed or unable to subm
155155

156156
- ***Note**: A question’s indicated cutoff value in the API is the threshold that Microsoft uses when analyzing your survey data. When you customize the cutoff value or Input Range, Microsoft analyzes your survey data according to your customization.
157157

158-
158+
<!--
159159
## Collect survey data
160160
161161
> [!IMPORTANT]
@@ -167,7 +167,7 @@ API will return the error messages when data validation failed or unable to subm
167167
You need to enable a Log Analytics Workspace to both store the log data of your surveys and access survey results. To enable these logs for your Communications Services, see: [Enable logging in Diagnostic Settings](../concepts/analytics/enable-logging.md). Follow the steps to add a diagnostic setting. Select the “ACSCallSurvey” data source when choosing category details. Also, choose “Send to Log Analytics workspace” as your destination detail.
168168
169169
- You can also integrate your Log Analytics workspace with Power BI, see: [Integrate Log Analytics with Power BI](../../../articles/azure-monitor/logs/log-powerbi.md)
170-
170+
-->
171171

172172
## Best Practices
173173
Here are our recommended survey flows and suggested question prompts for consideration. Your development can use our recommendation or use customized question prompts and flows for your visual interface.
@@ -191,10 +191,10 @@ Surveying Guidelines
191191
- Consider using surveys for separate ACS Resources in controlled experiments to identify release impacts.
192192

193193

194-
## Next Steps
194+
<!-- ## Next Steps
195195
196196
- Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
197197
198-
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md)
198+
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md) -->
199199

200200

0 commit comments

Comments
 (0)