Skip to content

Commit fc8f6d1

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into erguided
2 parents 96176f1 + 34eb1e8 commit fc8f6d1

31 files changed

+600
-248
lines changed

articles/analysis-services/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@
7070
href: analysis-services-vnet-gateway.md
7171
- name: Manage a server
7272
href: analysis-services-manage.md
73-
- name: Monitor
73+
- name: Monitor Analysis Services
7474
href: monitor-analysis-services.md
7575
- name: Set up diagnostic logging
7676
href: analysis-services-logging.md

articles/analysis-services/analysis-services-logging.md

Lines changed: 2 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -24,79 +24,9 @@ This article describes how to set up, view, and manage [Azure Monitor resource l
2424

2525
You can select **Engine**, **Service**, and **Metrics** log categories. For a listing of what's logged for each category, see [Supported resource logs for Microsoft.AnalysisServices/servers](monitor-analysis-services-reference.md#supported-resource-logs-for-microsoftanalysisservicesservers).
2626

27-
## Set up diagnostics logging
27+
## Set up diagnostic settings
2828

29-
### Azure portal
30-
31-
1. In [Azure portal](https://portal.azure.com) > server, click **Diagnostic settings** in the left navigation, and then click **Turn on diagnostics**.
32-
33-
![Screenshot showing Turn on diagnostics in the Azure portal.](./media/analysis-services-logging/aas-logging-turn-on-diagnostics.png)
34-
35-
2. In **Diagnostic settings**, specify the following options:
36-
37-
* **Name**. Enter a name for the logs to create.
38-
39-
* **Archive to a storage account**. To use this option, you need an existing storage account to connect to. See [Create a storage account](/azure/storage/common/storage-account-create). Follow the instructions to create a Resource Manager, general-purpose account, then select your storage account by returning to this page in the portal. It may take a few minutes for newly created storage accounts to appear in the drop-down menu.
40-
* **Stream to an event hub**. To use this option, you need an existing Event Hub namespace and event hub to connect to. To learn more, see [Create an Event Hubs namespace and an event hub using the Azure portal](/azure/event-hubs/event-hubs-create). Then return to this page in the portal to select the Event Hub namespace and policy name.
41-
* **Send to Azure Monitor (Log Analytics workspace)**. To use this option, either use an existing workspace or [create a new workspace](/azure/azure-monitor/logs/quick-create-workspace) resource in the portal. For more information on viewing your logs, see [View logs in Log Analytics workspace](#view-logs-in-log-analytics-workspace) in this article.
42-
43-
* **Engine**. Select this option to log xEvents. If you're archiving to a storage account, you can select the retention period for the resource logs. Logs are autodeleted after the retention period expires.
44-
* **Service**. Select this option to log service level events. If you are archiving to a storage account, you can select the retention period for the resource logs. Logs are autodeleted after the retention period expires.
45-
* **Metrics**. Select this option to store verbose data in [Metrics](analysis-services-monitor.md#server-metrics). If you are archiving to a storage account, you can select the retention period for the resource logs. Logs are autodeleted after the retention period expires.
46-
47-
3. Click **Save**.
48-
49-
If you receive an error that says "Failed to update diagnostics for \<workspace name>. The subscription \<subscription id> is not registered to use microsoft.insights." follow the [Troubleshoot Azure Diagnostics](../azure-monitor/essentials/resource-logs.md) instructions to register the account, then retry this procedure.
50-
51-
If you want to change how your resource logs are saved at any point in the future, you can return to this page to modify settings.
52-
53-
### PowerShell
54-
55-
Here are the basic commands to get you going. If you want step-by-step help on setting up logging to a storage account by using PowerShell, see the tutorial later in this article.
56-
57-
To enable metrics and resource logging by using PowerShell, use the following commands:
58-
59-
- To enable storage of resource logs in a storage account, use this command:
60-
61-
```powershell
62-
Set-AzDiagnosticSetting -ResourceId [your resource id] -StorageAccountId [your storage account id] -Enabled $true
63-
```
64-
65-
The storage account ID is the resource ID for the storage account where you want to send the logs.
66-
67-
- To enable streaming of resource logs to an event hub, use this command:
68-
69-
```powershell
70-
Set-AzDiagnosticSetting -ResourceId [your resource id] -ServiceBusRuleId [your service bus rule id] -Enabled $true
71-
```
72-
73-
The Azure Service Bus rule ID is a string with this format:
74-
75-
```powershell
76-
{service bus resource ID}/authorizationrules/{key name}
77-
```
78-
79-
- To enable sending resource logs to a Log Analytics workspace, use this command:
80-
81-
```powershell
82-
Set-AzDiagnosticSetting -ResourceId [your resource id] -WorkspaceId [resource id of the log analytics workspace] -Enabled $true
83-
```
84-
85-
- You can obtain the resource ID of your Log Analytics workspace by using the following command:
86-
87-
```powershell
88-
(Get-AzOperationalInsightsWorkspace).ResourceId
89-
```
90-
91-
You can combine these parameters to enable multiple output options.
92-
93-
### REST API
94-
95-
Learn how to [change diagnostics settings by using the Azure Monitor REST API](/rest/api/monitor/).
96-
97-
### Resource Manager template
98-
99-
Learn how to [enable diagnostics settings at resource creation by using a Resource Manager template](../azure-monitor/essentials/resource-manager-diagnostic-settings.md).
29+
To learn how to set up diagnostic settings using the Azure portal, Azure CLI, PowerShell, or Azure Resource Manager, see [Create diagnostic settings in Azure Monitor](/azure/azure-monitor/essentials/create-diagnostic-settings).
10030

10131
## Manage your logs
10232

articles/analysis-services/monitor-analysis-services-reference.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ See [Monitor Azure Analysis Services](monitor-analysis-services.md) for details
2020
### Supported metrics for Microsoft.AnalysisServices/servers
2121
The following table lists the metrics available for the Microsoft.AnalysisServices/servers resource type.
2222
[!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
23-
[!INCLUDE [Microsoft.AnalysisServices/servers](~/azure-reference-other-repo/azure-monitor-ref/supported-metrics/includes/microsoft-analysisservices-servers-metrics-include.md)]
23+
[!INCLUDE [Microsoft.AnalysisServices/servers](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-analysisservices-servers-metrics-include.md)]
2424

2525
[!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
2626
[!INCLUDE [horz-monitor-ref-metrics-dimensions](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]
@@ -29,7 +29,7 @@ Analysis Services metrics have the dimension `ServerResourceType`.
2929
[!INCLUDE [horz-monitor-ref-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-resource-logs.md)]
3030

3131
### Supported resource logs for Microsoft.AnalysisServices/servers
32-
[!INCLUDE [Microsoft.AnalysisServices/servers](~/azure-reference-other-repo/azure-monitor-ref/supported-logs/includes/microsoft-analysisservices-servers-logs-include.md)]
32+
[!INCLUDE [Microsoft.AnalysisServices/servers](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/logs/microsoft-analysisservices-servers-logs-include.md)]
3333

3434
When you set up logging for Analysis Services, you can select **Engine** or **Service** events to log.
3535

articles/analysis-services/monitor-analysis-services.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,11 @@ For a list of available metrics for Analysis Services, see [Analysis Services mo
3030

3131
[!INCLUDE [horz-monitor-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-logs.md)]
3232
- For the available resource log categories, associated Log Analytics tables, and the logs schemas for Analysis Services, see [Analysis Services monitoring data reference](monitor-analysis-services-reference.md#resource-logs).
33+
3334
## Analysis Services resource logs
3435

36+
To learn how to set up diagnostics logging, see [Set up diagnostic logging](analysis-services-logging.md).
37+
3538
When you set up logging for Analysis Services, you can select **Engine** or **Service** events to log, or select **AllMetrics** to log metrics data. For more information, see [Supported resource logs for Microsoft.AnalysisServices/servers](monitor-analysis-services-reference.md#supported-resource-logs-for-microsoftanalysisservicesservers).
3639

3740
[!INCLUDE [horz-monitor-activity-log](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-activity-log.md)]

articles/communication-services/how-tos/calling-sdk/call-transcription.md

Lines changed: 33 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,12 @@ ms.subservice: calling
99
ms.topic: how-to
1010
ms.date: 08/10/2021
1111
ms.custom: template-how-to
12-
zone_pivot_groups: acs-plat-ios-android-windows
13-
14-
#Customer intent: As a developer, I want to display the call transcription state on the client.
12+
zone_pivot_groups: acs-plat-web-ios-android-windows
1513
---
1614

1715
# Display call transcription state on the client
1816

19-
> [!NOTE]
20-
> Call transcription state is only available from Teams meetings. Currently there's no support for call transcription state for Azure Communication Services to Azure Communication Services calls.
21-
22-
When using call transcription you may want to let your users know that a call is being transcribe. Here's how.
17+
You need to collect consent from all participants in the call before you can transcribe them. Microsoft Teams allows users to start transcription in the meetings or calls. You would receive event when transcription has started on you can check the transcription state, if transcription started before you joined the call or meeting.
2318

2419
## Prerequisites
2520

@@ -28,6 +23,37 @@ When using call transcription you may want to let your users know that a call is
2823
- A user access token to enable the calling client. For more information, see [Create and manage access tokens](../../quickstarts/identity/access-tokens.md).
2924
- Optional: Complete the quickstart to [add voice calling to your application](../../quickstarts/voice-video-calling/getting-started-with-calling.md)
3025

26+
## Support
27+
The following tables define support of call transcription in Azure Communication Services.
28+
29+
## Identities and call types
30+
The following tables show support of transcription for specific call type and identity.
31+
32+
|Identities | Teams meeting | Room | 1:1 call | Group call | 1:1 Teams interop call | Group Teams interop call |
33+
|-----------------------------|---------------|------|----------|------------|------------------------|--------------------------|
34+
|Communication Services user | ✔️ | | | | ✔️ | ✔️ |
35+
|Microsoft 365 user | ✔️ | | | | ✔️ | ✔️ |
36+
37+
## Operations
38+
The following tables show support of individual APIs in calling SDK to individual identity types.
39+
40+
|Operations | Communication Services user | Microsoft 365 user |
41+
|-----------------------------|------------------------------|-------------------|
42+
|Get event that transcription has started | ✔️ | ✔️ |
43+
|Get transcription state | ✔️ | ✔️ |
44+
|Start or stop transcription | | |
45+
46+
## SDKs
47+
The following tables show support of transcription in individual Azure Communication Services SDKs.
48+
49+
| Platforms | Web | Web UI | iOS | iOS UI | Android | Android UI | Windows |
50+
|-------------|-----|--------|-----|--------|---------|------------|---------|
51+
|Is Supported | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
52+
53+
::: zone pivot="platform-web"
54+
[!INCLUDE [Call transcription client-side Web](./includes/call-transcription/call-transcription-web.md)]
55+
::: zone-end
56+
3157
::: zone pivot="platform-android"
3258
[!INCLUDE [Call transcription client-side Android](./includes/call-transcription/call-transcription-android.md)]
3359
::: zone-end
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
author: tomaschladek
3+
ms.service: azure-communication-services
4+
ms.topic: include
5+
ms.date: 08/08/2024
6+
ms.author: tchladek
7+
---
8+
9+
[!INCLUDE [Install SDK](../install-sdk/install-sdk-web.md)]
10+
11+
> [!WARNING]
12+
> Due to changes in Microsoft Teams, JavaScript calling SDKs with versions 1.21 and lower stops Teams transcription and blocks Teams users to start transcription. If you would like to leverage Teams transcription in the calls and meetings, you need to upgrade your calling SDK to at least version 1.22.
13+
14+
## Call transcription
15+
16+
`Transcription` is an extended feature of the class `Call`. You first need to obtain the transcription feature API object
17+
18+
```js
19+
const callTranscriptionFeature = call.feature(Features.Transcription);
20+
```
21+
22+
You can check state of the transcription in the property `isTranscriptionActive`. If value is set to `true`, then transcription is active.
23+
24+
```js
25+
const isTranscriptionActive = callTranscriptionFeature.isTranscriptionActive;
26+
```
27+
28+
You can subscribe to event that is triggered when state of transcription changes:
29+
30+
```js
31+
const isTranscriptionActiveChangedHandler = () => {
32+
console.log(callTranscriptionFeature.isTranscriptionActive);
33+
};
34+
callTranscriptionFeature.on('isTranscriptionActiveChanged', isTranscriptionActiveChangedHandler);
35+
```
36+
37+
You can unsubscribe from the event with the following code:
38+
39+
```js
40+
callTranscriptionFeature.off('isTranscriptionActiveChanged', isTranscriptionActiveChangedHandler);
41+
```

articles/communication-services/quickstarts/voice-video-calling/includes/data-channel/data-channel-android.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: include
1010
ms.service: azure-communication-services
1111
ms.subservice: calling
1212
---
13-
[!INCLUDE [Public Preview](../../../../includes/public-preview-include-document.md)]
13+
1414
>[!IMPORTANT]
1515
> Please be aware that the current Data Channel feature API doesn't support direct messaging between a web browser and a native app in a peer-to-peer call scenario.
1616

articles/communication-services/quickstarts/voice-video-calling/includes/data-channel/data-channel-ios.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ ms.service: azure-communication-services
1111
ms.subservice: calling
1212
---
1313

14-
[!INCLUDE [Public Preview](../../../../includes/public-preview-include-document.md)]
1514
>[!IMPORTANT]
1615
> Please be aware that the current Data Channel feature API doesn't support direct messaging between a web browser and a native app in a peer-to-peer call scenario.
1716

articles/communication-services/quickstarts/voice-video-calling/includes/data-channel/data-channel-windows.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ ms.service: azure-communication-services
1111
ms.subservice: calling
1212
---
1313

14-
[!INCLUDE [Public Preview](../../../../includes/public-preview-include-document.md)]
1514
>[!IMPORTANT]
1615
> Please be aware that the current Data Channel feature API doesn't support direct messaging between a web browser and a native app in a peer-to-peer call scenario.
1716

articles/ddos-protection/test-through-simulations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -218,7 +218,7 @@ RedWolf's [DDoS Testing](https://www.redwolfsecurity.com/services/) service suit
218218

219219
- **Attack Vectors**: Unique cloud attacks designed by RedWolf. For more information about RedWolf attack vectors, see [Technical Details](https://www.redwolfsecurity.com/redwolf-technical-details/).
220220
- **Guided Service**: Leverage RedWolf's team to run tests. For more information about RedWolf's guided service, see [Guided Service](https://www.redwolfsecurity.com/managed-testing-explained/).
221-
- **Self Service**: Leverage RedWol to run tests yourself. For more information about RedWolf's self-service, see [Self Service](https://www.redwolfsecurity.com/self-serve-testing/).
221+
- **Self Service**: Leverage RedWolf to run tests yourself. For more information about RedWolf's self-service, see [Self Service](https://www.redwolfsecurity.com/self-serve-testing/).
222222

223223
## MazeBolt
224224

0 commit comments

Comments
 (0)