One order. Four teams need to know.

Frequently asked questions

Why publish one OrderPlaced event instead of calling each service directly?

Calling email, inventory and shipping directly from checkout means every new consumer requires editing the checkout code — and one of those calls failing can fail the whole order. Publishing one event and letting each team subscribe with its own filter decouples them completely.

What happens if a subscriber can't process an Event Grid event?

Event Grid retries delivery for a period before the event is dead-lettered, so a temporarily-down subscriber doesn't silently lose events — but a subscriber that's broken for good needs its own alert on dead-letter volume.

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

• AI Bot Attacks on a Mobile App Login, and How Azure Stops Them

  A script tries 8,000 passwords a minute against your login API at 3am. Rate limiting, smart lockout and Defender for Cloud make speed the losing move.

• Azure Key Vault Explained: The One Secret Tutorials Never Remove

  Moving every secret into Key Vault leaves exactly one behind: the credential that opens the vault. A managed identity is what removes it.

• How to Secure a Mobile API on Azure in Five Steps, in the Right Order

  HTTPS only, authentication, authorization, secrets and monitoring: five steps to secure a mobile API on Azure, and why the order carries most of the value.