Skip to content

Commit a3199ed

Browse files
Merge pull request #284103 from spelluru/egridga0808
removed Preview
2 parents ee8f08c + d98ee01 commit a3199ed

File tree

3 files changed

+7
-1
lines changed

3 files changed

+7
-1
lines changed

articles/event-grid/custom-domains-namespaces.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ The Event Grid namespace is automatically assigned an HTTP hostname at the time
1414

1515
You can assign your custom domain names to your Event Grid namespace’s MQTT and HTTP host names, along with the default host names. Custom domain configurations not only help you to meet your security and compliance requirements, but also eliminates the need to modify your clients that are already linked to your domain.
1616

17+
> [!NOTE]
18+
> This feature is currently in preview.
19+
1720
## High-level steps
1821

1922
To use custom domains for namespaces, follow these steps:

articles/event-grid/includes/limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Event Grid offers a standard tier and basic tier. Event Grid standard tier enabl
1818

1919
## Event Grid Namespace resource limits
2020

21-
[Azure Event Grid namespaces](../concepts-event-grid-namespaces.md#namespaces) is available in public preview and enables MQTT messaging, and HTTP pull delivery.
21+
[Azure Event Grid namespaces](../concepts-event-grid-namespaces.md#namespaces) enables MQTT messaging, and HTTP pull delivery.
2222
The following limits apply to namespace resources in Azure Event Grid.
2323

2424
| Limit description | Limit |

articles/event-grid/oauth-json-web-token-authentication.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ This article shows how to authenticate with Azure Event Grid namespace using JSO
1414

1515
OAuth 2.0 (JSON Web Token) authentication allows clients to authenticate and connect with the MQTT broker using JSON Web Tokens (JWT) issued by any OpenID Connect identity provider, apart from Microsoft Entra ID. MQTT clients can get their token from their identity provider and provide the token in the MQTTv5 or MQTTv3.1.1 CONNECT packets to authenticate with the MQTT broker. This authentication method provides a lightweight, secure, and flexible option for MQTT clients that aren't provisioned in Azure.
1616

17+
> [!NOTE]
18+
> This feature is currently in preview.
19+
1720
## High-level steps
1821

1922
To use custom JWT authentication for namespaces, follow these steps:

0 commit comments

Comments
 (0)