Skip to content

Commit f8620e4

Browse files
Merge pull request #275005 from spelluru/git122046
No blob storage needed
2 parents 41a8972 + 2b0d907 commit f8620e4

File tree

2 files changed

+3
-58
lines changed

2 files changed

+3
-58
lines changed

articles/event-grid/authenticate-with-entra-id-namespaces.md

Lines changed: 1 addition & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ EventGridEvent egEvent = new EventGridEvent(
8585
await client.SendEventAsync(egEvent);
8686
```
8787

88-
### Prerequisites
88+
### SDKs
8989

9090
Following are the prerequisites to authenticate to Event Grid.
9191

@@ -124,61 +124,6 @@ For more information, see the following articles:
124124
- [Azure Event Grid client library for JavaScript](/javascript/api/overview/azure/eventgrid-readme)
125125
- [Azure Event Grid client library for Python](/python/api/overview/azure/eventgrid-readme)
126126

127-
## Disable key and shared access signature authentication
128-
129-
Microsoft Entra authentication provides a superior authentication support than that's offered by access key or Shared Access Signature (SAS) token authentication. With Microsoft Entra authentication, the identity is validated against Microsoft Entra identity provider. As a developer, you won't have to handle keys in your code if you use Microsoft Entra authentication. You'll also benefit from all security features built into the Microsoft Identity platform, such as [Conditional Access](/entra/identity/conditional-access/overview) that can help you improve your application's security stance.
130-
131-
Once you decide to use Microsoft Entra authentication, you can disable authentication based on access keys or SAS tokens.
132-
133-
> [!NOTE]
134-
> Acess keys or SAS token authentication is a form of **local authentication**. you'll hear sometimes referring to "local auth" when discussing this category of authentication mechanisms that don't rely on Microsoft Entra ID. The API parameter used to disable local authentication is called, appropriately so, ``disableLocalAuth``.
135-
136-
### Azure portal
137-
138-
When creating a new topic, you can disable local authentication on the **Advanced** tab of the **Create Topic** page.
139-
140-
:::image type="content" source="./media/authenticate-with-microsoft-entra-id/create-topic-disable-local-auth.png" alt-text="Screenshot showing the Advanced tab of Create Topic page when you can disable local authentication.":::
141-
142-
For an existing topic, following these steps to disable local authentication:
143-
144-
1. Navigate to the **Event Grid Topic** page for the topic, and select **Enabled** under **Local Authentication**
145-
146-
:::image type="content" source="./media/authenticate-with-microsoft-entra-id/existing-topic-local-auth.png" alt-text="Screenshot showing the Overview page of an existing topic.":::
147-
2. In the **Local Authentication** popup window, select **Disabled**, and select **OK**.
148-
149-
:::image type="content" source="./media/authenticate-with-microsoft-entra-id/local-auth-popup.png" alt-text="Screenshot showing the Local Authentication window.":::
150-
151-
152-
### Azure CLI
153-
The following CLI command shows the way to create a custom topic with local authentication disabled. The disable local auth feature is currently available as a preview and you need to use API version ``2021-06-01-preview``.
154-
155-
```cli
156-
az resource create --subscription <subscriptionId> --resource-group <resourceGroup> --resource-type Microsoft.EventGrid/topics --api-version 2021-06-01-preview --name <topicName> --location <location> --properties "{ \"disableLocalAuth\": true}"
157-
```
158-
159-
For your reference, the following are the resource type values that you can use according to the topic you're creating or updating.
160-
161-
| Topic type | Resource type |
162-
| ------------------| :------------------------------------|
163-
| Domains | Microsoft.EventGrid/domains |
164-
| Partner Namespace | Microsoft.EventGrid/partnerNamespaces|
165-
| Custom Topic | Microsoft.EventGrid/topics |
166-
167-
### Azure PowerShell
168-
169-
If you're using PowerShell, use the following cmdlets to create a custom topic with local authentication disabled.
170-
171-
```PowerShell
172-
173-
Set-AzContext -SubscriptionId <SubscriptionId>
174-
175-
New-AzResource -ResourceGroupName <ResourceGroupName> -ResourceType Microsoft.EventGrid/topics -ApiVersion 2021-06-01-preview -ResourceName <TopicName> -Location <Location> -Properties @{disableLocalAuth=$true}
176-
```
177-
178-
> [!NOTE]
179-
> - To learn about using the access key or shared access signature authentication, see [Authenticate publishing clients with keys or SAS tokens](security-authenticate-publishing-clients.md)
180-
> - This article deals with authentication when publishing events to Event Grid (event ingress). Authenticating Event Grid when delivering events (event egress) is the subject of article [Authenticate event delivery to event handlers](security-authentication.md).
181-
182127
## Resources
183128
- Data plane SDKs
184129
- Java SDK: [GitHub](https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/eventgrid/azure-messaging-eventgrid) | [samples](https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/eventgrid/azure-messaging-eventgrid/src/samples/java/com/azure/messaging/eventgrid) | [migration guide from previous SDK version](https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/eventgrid/azure-messaging-eventgrid/migration-guide.md)

articles/event-grid/custom-event-quickstart-portal.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Before you create a subscription for the custom topic, create an endpoint for th
5858
:::image type="content" source="~/reusable-content/ce-skilling/azure/media/template-deployments/deploy-to-azure-button.svg" alt-text="Button to deploy the Resource Manager template to Azure." border="false" link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure-Samples%2Fazure-event-grid-viewer%2Fmaster%2Fazuredeploy.json":::
5959

6060
2. On the **Custom deployment** page, do the following steps:
61-
1. For **Resource group**, select the resource group that you created when creating the storage account. It will be easier for you to clean up after you're done with the tutorial by deleting the resource group.
61+
1. For **Resource group**, select an existing resource group or create a resource group.
6262
2. For **Site Name**, enter a name for the web app.
6363
3. For **Hosting plan name**, enter a name for the App Service plan to use for hosting the web app.
6464
5. Select **Review + create**.
@@ -68,7 +68,7 @@ Before you create a subscription for the custom topic, create an endpoint for th
6868
1. The deployment may take a few minutes to complete. Select Alerts (bell icon) in the portal, and then select **Go to resource group**.
6969

7070
:::image type="content" source="./media/blob-event-quickstart-portal/navigate-resource-group.png" alt-text="Screenshot showing the successful deployment message with a link to navigate to the resource group.":::
71-
4. On the **Resource group** page, in the list of resources, select the web app that you created. You also see the App Service plan and the storage account in this list.
71+
4. On the **Resource group** page, in the list of resources, select the web app (**contosoegriviewer** in the following example) that you created.
7272

7373
:::image type="content" source="./media/blob-event-quickstart-portal/resource-group-resources.png" alt-text="Screenshot that shows the Resource Group page with the deployed resources.":::
7474
5. On the **App Service** page for your web app, select the URL to navigate to the web site. The URL should be in this format: `https://<your-site-name>.azurewebsites.net`.

0 commit comments

Comments
 (0)