You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The **Network Diagnostics Tool** enables Azure Communication Services developers to ensure that their device and network conditions are optimal for connecting to the service to ensure a great call experience. The tool can be found at [aka.ms/acsdiagnostics](https://azurecommdiagnostics.net/). Users can quickly run a test, by pressing the start test button. The tool performs diagnostics on the network, devices, and call quality. The results of the diagnostics are directly provided through the tools UI. No sign-in required to use the tool. After the test, a GUID is presented which can be provided to our support team for further help.
19
19
20
20
21
21
22
22
As part of the diagnostics performed, the user is asked to enable permissions for the tool to access their devices. Next, the user is asked to record their voice, which is then played back using an echo bot to ensure that the microphone is working. The tool finally, performs a video test. The test uses the camera to detect video and measure the quality for sent and received frames.
23
23
24
-
If you are looking to build your own Network Diagnostic Tool or to perform deeper integration of this tool into your application, you can levearge[pre-call diagnostic APIs](../voice-video-calling/pre-call-diagnostics.md) for the calling SDK.
24
+
If you are looking to build your own Network Diagnostic Tool or to perform deeper integration of this tool into your application, you can leverage[pre-call diagnostic APIs](../voice-video-calling/pre-call-diagnostics.md) for the calling SDK.
25
25
26
26
## Performed tests
27
27
@@ -31,7 +31,6 @@ If you are looking to build your own Network Diagnostic Tool or to perform deepe
| Browser Diagnostic | Checks for browser compatibility. Azure Communication Services supports specific browsers for [calling](../voice-video-calling/calling-sdk-features.md#javascript-calling-sdk-support-by-os-and-browser) and [chat](../chat/sdk-features.md#javascript-chat-sdk-support-by-os-and-browser). |
33
33
| Media Device Diagnostic | Checks for availability of device (camera, microphone and speaker) and enabled permissions for those devices on the browser. |
34
-
| Service Connectivity | Checks whether it can connect to Azure Communication Services |
35
34
| Audio Test | Performs an echo bot call. Here the user can talk to echo bot and hear themselves back. The test records media quality statistics for audio including jitter, bitrate, packet loss and RTT with thresholds for optimal conditions. |
36
35
| Video Test | Performs a loop back video test, where video captured by the camera is sent back and forth to check for network quality conditions. The test records media quality statistics for video including jitter, bitrate, packet loss and RTT with thresholds for optimal conditions. |
37
36
@@ -48,5 +47,4 @@ The test provides a **unique identifier** for your test which you can provide ou
48
47
-[Use Pre-Call Diagnostic APIs to build your own tech check](../voice-video-calling/pre-call-diagnostics.md)
Copy file name to clipboardExpand all lines: articles/event-grid/event-domains.md
+9-29Lines changed: 9 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,42 +2,31 @@
2
2
title: Event Domains in Azure Event Grid
3
3
description: This article describes how to use event domains to manage the flow of custom events to your various business organizations, customers, or applications.
4
4
ms.topic: conceptual
5
-
ms.date: 04/13/2021
5
+
ms.date: 11/17/2022
6
6
---
7
7
8
8
# Understand event domains for managing Event Grid topics
9
-
10
-
This article describes how to use event domains to manage the flow of custom events to your various business organizations, customers, or applications. Use event domains to:
9
+
An event domain is a management tool for large number of Event Grid topics related to the same application. You can think of it as a meta-topic that can have thousands of individual topics. It allows an event publisher to publish events to thousands of topics at the same time. Domains also give you authentication and authorization control over each topic so you can partition your tenants. This article describes how to use event domains to manage the flow of custom events to your various business organizations, customers, or applications. Use event domains to:
11
10
12
11
* Manage multitenant eventing architectures at scale.
13
-
* Manage your authorization and authentication.
12
+
* Manage your authentication and authorization.
14
13
* Partition your topics without managing each individually.
15
14
* Avoid individually publishing to each of your topic endpoints.
16
15
17
-
## Event domain overview
18
-
19
-
An event domain is a management tool for large numbers of Event Grid topics related to the same application. You can think of it as a meta-topic that can have thousands of individual topics.
20
-
21
-
Event domains provide you the same architecture used by Azure services like Storage and IoT Hub to publish their events. They allow you to publish events to thousands of topics. Domains also give you authorization and authentication control over each topic so you can partition your tenants.
With a domain, you get fine grain authorization and authentication control over each topic via Azure role-based access control (Azure RBAC). You can use these roles to restrict each tenant in your application to only the topics you wish to grant them access to.
29
-
30
-
Azure RBAC in event domains works the same way [managed access control](security-authorization.md) works in the rest of Event Grid and Azure. Use Azure RBAC to create and enforce custom role definitions in event domains.
21
+
With a domain, you get fine grain authorization and authentication control over each topic via Azure role-based access control (Azure RBAC). You can use these roles to restrict each tenant in your application to only the topics you wish to grant them access to. Azure RBAC in event domains works the same way [managed access control](security-authorization.md) works in the rest of Event Grid and Azure. Use Azure RBAC to create and enforce custom role definitions in event domains.
31
22
32
23
### Built in roles
33
24
34
-
Event Grid has two built-in role definitions to make Azure RBAC easier for working with event domains. These roles are **EventGrid EventSubscription Contributor (Preview)** and **EventGrid EventSubscription Reader (Preview)**. You assign these roles to users who need to subscribe to topics in your event domain. You scope the role assignment to only the topic that users need to subscribe to.
35
-
36
-
For information about these roles, see [Built-in roles for Event Grid](security-authorization.md#built-in-roles).
25
+
Event Grid has two built-in role definitions to make Azure RBAC easier for working with event domains. These roles are **EventGrid EventSubscription Contributor** and **EventGrid EventSubscription Reader**. You assign these roles to users who need to subscribe to topics in your event domain. You scope the role assignment to only the topic that users need to subscribe to. For information about these roles, see [Built-in roles for Event Grid](security-authorization.md#built-in-roles).
37
26
38
27
## Subscribing to topics
39
28
40
-
Subscribing to events on a topic within an event domain is the same as [creating an Event Subscription on a custom topic](./custom-event-quickstart.md) or subscribing to an event from an Azure service.
29
+
Subscribing to events for a topic within an event domain is the same as [creating an Event Subscription on a custom topic](./custom-event-quickstart.md) or subscribing to an event from an Azure service.
41
30
42
31
> [!IMPORTANT]
43
32
> Domain topic is considered an **auto-managed** resource in Event Grid. You can create an event subscription at the [domain scope](#domain-scope-subscriptions) without creating the domain topic. In this case, Event Grid automatically creates the domain topic on your behalf. Of course, you can still choose to create the domain topic manually. This behavior allows you to worry about one less resource when dealing with a huge number of domain topics. When the last subscription to a domain topic is deleted, the domain topic is also deleted irrespective of whether the domain topic was manually created or auto-created.
@@ -48,11 +37,7 @@ Event domains also allow for domain-scope subscriptions. An event subscription o
48
37
49
38
## Publishing to an event domain
50
39
51
-
When you create an event domain, you're given a publishing endpoint similar to if you had created a topic in Event Grid.
52
-
53
-
To publish events to any topic in an Event Domain, push the events to the domain's endpoint the [same way you would for a custom topic](./post-to-custom-topic.md). The only difference is that you must specify the topic you'd like the event to be delivered to.
54
-
55
-
For example, publishing the following array of events would send event with `"id": "1111"` to topic `foo` while the event with `"id": "2222"` would be sent to topic `bar`:
40
+
When you create an event domain, you're given a publishing endpoint similar to if you had created a topic in Event Grid. To publish events to any topic in an event domain, push the events to the domain's endpoint the [same way you would for a custom topic](./post-to-custom-topic.md). The only difference is that you must specify the topic you'd like the event to be delivered to. For example, publishing the following array of events would send event with `"id": "1111"` to topic `foo` while the event with `"id": "2222"` would be sent to topic `bar`:
56
41
57
42
```json
58
43
[{
@@ -95,12 +80,7 @@ Here are the limits and quotas related to event domains:
Event domains use the same [operations pricing](https://azure.microsoft.com/pricing/details/event-grid/) that all other features in Event Grid use.
99
-
100
-
Operations work the same in event domains as they do in custom topics. Each ingress of an event to an event domain is an operation, and each delivery attempt for an event is an operation.
101
-
102
-
83
+
Event domains use the same [operations pricing](https://azure.microsoft.com/pricing/details/event-grid/) that all other features in Event Grid use. Operations work the same in event domains as they do in custom topics. Each ingress of an event to an event domain is an operation, and each delivery attempt for an event is an operation.
103
84
104
85
## Next steps
105
-
106
-
* To learn about setting up event domains, creating topics, creating event subscriptions, and publishing events, see [Manage event domains](./how-to-event-domains.md).
86
+
To learn about setting up event domains, creating topics, creating event subscriptions, and publishing events, see [Manage event domains](./how-to-event-domains.md).
Copy file name to clipboardExpand all lines: articles/event-grid/event-schema-key-vault.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
title: Azure Key Vault as Event Grid source
3
3
description: Describes the properties and schema provided for Azure Key Vault events with Azure Event Grid
4
4
ms.topic: conceptual
5
-
ms.date: 09/15/2021
5
+
ms.date: 11/17/2022
6
6
---
7
7
8
8
# Azure Key Vault as Event Grid source
9
9
10
-
This article provides the properties and schema for events in [Azure Key Vault](../key-vault/index.yml). For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md).
10
+
This article provides the properties and schema for events in [Azure Key Vault](../key-vault/index.yml). For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md) and [Cloud event schema](cloud-event-schema.md).
0 commit comments