Provisioning an Event Grid Topic

1. Start Locally

Firstly, we need to launch Locally which we can do from a terminal by running:

Once Locally has started, the Locally Dashboard will open automatically:

2. Create a Resource Group

Next we can create the Resource Group:

There's two things to note here:

1. The Azure CLI supports Automatic Configuration, meaning that it can automatically be configured to work against Locally just by prefixing commands with locally run.
2. Locally intentionally uses a different set of locations to Azure as a safety precaution, so that you can be confident you're deploying against Locally rather than regular Azure. You can also configure Locally to use the Azure locations too, but you'll want to be extra sure that you're prefixing commands with locally run when you do.

3. Create the Event Grid Topic

With the Resource Group in place, we can create the Event Grid Topic - the endpoint publishers send events to:

{
  "endpoint": "https://sample-topic-berlin.eventgrid.locally:5662/api/events",
  "name": "sample-topic",
  "state": "Succeeded"
}

That eventgrid.locally hostname is served by Locally's own DNS server and points at the Event Grid Emulator running on your machine.

4. Get a publishing key

Publishing to a topic needs a key as well as the endpoint:

Together with the endpoint above, that's everything an SDK needs to publish events.

We can list the topics in the Resource Group:

We can see the Event Grid Topic in the Locally Dashboard too:

5. Tidy up

Finally, we can tidy up. To remove the Resource Group and everything within it:

There's nothing billable to clean up, since everything ran on your machine, but it's still worth checking your teardown scripts work here before you run them against Azure.

Doing this with other tooling

Whilst this guide used the Azure CLI, Event Grid works the same way through any of the tooling that Locally supports - a Microsoft.EventGrid/topics resource in HashiCorp Terraform or OpenTofu, Pulumi, Bicep or an ARM Template all provision against Locally in the same way, with only the location changed.

Next steps

The Event Grid Emulator lets you publish events from the browser and see each delivery. To handle events in code, see Function App.

Should you encounter any issues, please take a look at the troubleshooting section.