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
Copy file name to clipboardExpand all lines: articles/event-grid/auth0-how-to.md
+62-1Lines changed: 62 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,4 +7,65 @@ author: banisadr
7
7
ms.service: event-grid
8
8
ms.date: 05/18/2020
9
9
ms.author: babanisa
10
-
---
10
+
---
11
+
12
+
Integrate Azure Event Grid with Auth0
13
+
In this article
14
+
Azure’s Event Grid is a serverless event bus that acts as an intermediary allowing you to send data from Auth0 into the Azure ecosystem.
15
+
You can create an event-driven workflow using Event Grid to send your Auth0 tenant logs to the targets of your choice (e.g., Azure Functions, Event Hubs, Sentinel and Logic Apps).
16
+
See the Auth0 event type codes for a full list of the events that Auth0 supports
17
+
Send events from Auth0 to Azure Event Grid
18
+
To send Auth0 events to Azure, you will need:
19
+
Enable Event Grid resource provider
20
+
Set up an event source (in this case, this is Auth0).
21
+
Set up an event handler, the app or service where the event will be sent.
22
+
For more information about these concepts, see Concepts in Azure Event Grid
23
+
Enable Event Grid resource provider
24
+
If you haven’t previously used Event Grid, you will need to register the Event Grid resource provider. If you’ve used Event Grid before, skip to the next section.
25
+
26
+
In your Azure portal:
27
+
Select Subscriptions on the left menu
28
+
Select the subscription you’re using for Event Grid
29
+
On the left menu, under Settings, select Resource providers
30
+
Find Microsoft.EventGrid
31
+
Select Register
32
+
Refresh to make sure the status changes to Registered
33
+
Set up an Auth0 event source
34
+
Part of the integration process is to set Auth0 up for use as an event source (this step happens on your Dashboard).
35
+
Log in to the Auth0 Dashboard.
36
+
Navigate to Logs > Streams.
37
+
Click + Create Stream.
38
+
Select Azure Event Grid and enter a unique name for your new stream.
39
+
Create the event source by providing your Azure Subscription ID, Azure Region and a Resource Group name.
40
+
Click Save.
41
+
Go to the Azure Portal to complete the final steps of the integration.
42
+
Set up an event handler
43
+
Go to your Azure subscription and spin up a service that is supported as an event handler (for a full list of all supported event handlers go to this article).
44
+
Activate your Auth0 Partner Topic in Azure
45
+
Activating the Auth0 topic in Azure allows events to flow from Auth0 to Azure.
46
+
Log in to the Azure Portal.
47
+
Search `Partner Topics` at the top and click `Event Grid Partner Topics` under services.
48
+
Click on the topic that matches the stream you created in your Auth0 Dashboard.
49
+
Confirm the `Source` field matches your Auth0 account.
50
+
Click Activate.
51
+
52
+
Subscribe to your Auth0 Partner Topic
53
+
You subscribe to an event grid topic to tell Event Grid which events to send to which event handler.
54
+
On the Event Grid topic page, select + Event Subscription on the toolbar
55
+
On the Create Event Subscription page:
56
+
Enter a name for the event subscription.
57
+
Select your desired Azure service or WebHook for the Endpoint type.
58
+
Follow the instructions for the particular service.
59
+
Back on the Create Event Subscription page, select Create.
60
+
To send events to your topic, please follow the instructions on this article.
61
+
Testing
62
+
At this point, your Event Grid workflow should be complete.
63
+
Verify the integration
64
+
To verify that the integration is working as expected:
65
+
Log in to the Auth0 Dashboard.
66
+
Navigate to Logs > Streams.
67
+
Click on your Event Grid stream.
68
+
Once on the stream, click on the Health tab. The stream should be active and as long as you don't see any errors, the stream is working.
69
+
Delivery attempts and retries
70
+
Auth0 events are delivered to AWS via a streaming mechanism that sends each event as it is triggered in our system. If EventBridge is unable to receive the event, we will retry up to three times to deliver the event; otherwise, we will log the failure to deliver in our system.
Blurb: Auth0, the identity platform for application builders, provides developers and enterprises with the building blocks they need to secure their applications.
19
+
20
+
Description
21
+
22
+
Partnering with Event Grid allows our customers to leverage events emitted by Auth0’s system to accomplish a number of use cases, from engaging with users in meaningful and custom ways after the authentication to automating security and infrastructure tasks.
23
+
24
+
The Auth0 Partner Topic integration allows you to stream your Auth0 log events with high reliability into Azure for consumption with any of your favorite Azure resources. This will allow you to react to events, gain insights, monitor for security issues, and interact with other powerful data pipelines.
25
+
26
+
For organizations using Auth0 and Azure, this integration will allow you to seamlessly integrate data across your entire stack. Here is a quick overview of the use cases this integration unlocks:
27
+
28
+
29
+
Engage with Your Users
30
+
Delivering a strong user experience is critical to reducing churn and retaining users. Using Auth0 log events and Azure Functions and Azure Logic Apps, you can deliver more customized application experiences.
31
+
Understand User Behavior
32
+
Understanding when users access your product, where they are signed in from, and what devices they use are important pieces of information that can drive your product development. By keeping track of these signals, via the log events emitted by Auth0, you can develop an understanding of the product areas that you should be paying attention to. These signals can help you determine what browsers and devices to support, what languages to consider localizing your app in, and when your peak application traffic times are.
33
+
Manage User Data
34
+
Retaining and auditing user actions is crucial for maintaining security and complying with industry regulations. Besides, the ability to edit, remove, or export user data upon request is becoming increasingly important to comply with various data privacy laws, such as the European Union’s General Data Protection Regulation (GDPR).
35
+
Secure Your Application
36
+
Consolidating security monitoring and incident response procedures is important when protecting a distributed system. For this reason it is important to keep all the data in one place and monitor the entire stack.
37
+
38
+
Creating an Auth0 Partner Topic
39
+
40
+
Note the Azure Subscription and Resource Group you want the Partner Topic to be created in.
41
+
Log in to your Auth0 account dashboard. Navigate to Logs > Streams, click “Create Stream” and select the “Azure Event Grid” event stream.
42
+
Provide the Azure Subscription ID, Resource Group and other required information and click “Save”
43
+
View your pending Partner Topics in Azure and activate the topic to allow events to flow.
44
+
45
+
Go To Button Link: https://auth0.com/docs/logs/streams/azure-eventgrid
Copy file name to clipboardExpand all lines: articles/event-grid/partner-onboarding-how-to.md
+38-1Lines changed: 38 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,4 +7,41 @@ author: banisadr
7
7
ms.service: event-grid
8
8
ms.date: 05/18/2020
9
9
ms.author: babanisa
10
-
---
10
+
---
11
+
12
+
13
+
## Prerequisites
14
+
15
+
1. Please contact Azure Event Grid team ([email protected]) with a list of Azure subscriptions to be whitelisted in order to be allowed to try this feature.
16
+
1. As of 01/15/2020, partner topic support is available in centraluseuap only; hence this sample code can used in this region only.
17
+
1. The following resources are expected to be pre-created and ready to be used:
18
+
* At least one valid Azure Subscription, although the scenario is designed for three different Azure Subscriptions to be used for partner registration, namespaces/eventchannels, and partner topics, respectively. The first two Azure subscriptions are expected to be owned by the partner and the last one is owned by the user/customer.
19
+
* At least one valid resource group. Similar to the Azure Subscriptions point above in 3.a, the scenario is also designed for three different resource groups, one for each Azure Subscription, to be used for partner registration, namespaces/eventchannels, and partner topics, respectively.
20
+
21
+
The first two Azure subscriptions/Resource Groups are expected to be owned by the partner and the last one is owned by the user/customer.
22
+
1. Registrered App Id, and tenant Id. For simplicity, this console app assumes the same for both partner and customer but code can be updated to allow different values.
23
+
1. Valid certificate which is associated with the AppId to be installed on the machine.
24
+
1. Valid storage account and storage queue to be used as an event subscription destination. Here is a link for doing that using portal https://docs.microsoft.com/en-us/azure/storage/queues/storage-quickstart-queues-portal and cli https://docs.microsoft.com/en-us/cli/azure/storage/queue?view=azure-cli-latest
25
+
1. Fill out these required information in the App.Config file. Each entry is marked with Placeholder in the comment in the App.Config file.
26
+
1. Open the project using Visual Studio 2017 or higher. Build and run.
27
+
## Scenario Flow
28
+
29
+
The overall flow of the scenario demoed in the sample code is:
Copy file name to clipboardExpand all lines: articles/event-grid/partner-topics-overview.md
+24-1Lines changed: 24 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,4 +7,27 @@ author: banisadr
7
7
ms.service: event-grid
8
8
ms.date: 05/18/2020
9
9
ms.author: babanisa
10
-
---
10
+
---
11
+
12
+
# Partner Topics in Azure Event Grid (Preview)
13
+
Partner Topics allow you to connect 3rd party event sources, such as SaaS and PaaS solutions, directly to Event Grid. This allows you to subscribe to events from partners in the same way you are able to subscribe to events from other Azure services, such as Azure Storage and IoT Hub.
14
+
15
+
## Available Partners
16
+
The first partner available through Event Grid Partner Topics is Auth0. The [Auth0 partner topic](auth0-overview.md) enables you to connect your Auth0 and Azure accounts in order to react to, log, and monitor Auth0 events in real time.
17
+
18
+
[Try it out](auth0-how-to.md) today by logging in to your Auth0 account and creating an Event Grid integration. Once you click create in Auth0, you’ll see a pending Auth0 Topic in your Azure account. Click activate and you’ll be able to create Event Subscriptions, route, filter, and deliver your events just as you do any other event source.
19
+
20
+
## Pricing
21
+
Partner topics are charged at the same operation rate as system topics.
22
+
23
+
## Limits
24
+
Partner Topics are in Public Preview. During public preview, Partner topics are subject to the [same limits](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#event-grid-limits) as system topics and custom topics.
25
+
26
+
## How do I become an Event Grid partner?
27
+
The infrastructure created to support this launch makes it easy and quick for new partners to integrate their eventing capabilities with Event Grid. Read the [partner onboarding documentation](partner-onboarding-how-to.md) for more.
28
+
29
+
## Next steps
30
+
31
+
-[Auth0 Partner Topic](auth0-overview.md)
32
+
-[How to use the Auth0 Partner Topic](auth0-how-to.md)
33
+
-[Become an Event Grid partner](partner-onboarding-how-to.md)
0 commit comments