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.

• How Azure Protects a Mobile App: The Full Request Flow, Layer by Layer

  Front Door, your API, Microsoft Entra ID, authorization and a private database — the five layers that stand between a mobile app and its data on Azure.

• Your Mobile App Is Leaking Its API Key — and Obfuscation Will Not Save It

  An APK or IPA is a zip file. Anything hardcoded inside it, including your API key, is already public — and here is how to get it off the phone for good.

• What Is Microsoft Foundry (Azure AI Foundry)? The Services, and When You Actually Need Them

  A plain tour of Microsoft Foundry for developers: the resource, projects, models, agents, tools, and when Azure OpenAI on its own is enough.