Testing
Azure Service Bus is Microsoft's enterprise messaging platform for decoupled, reliable communication between services. Testing it properly means verifying message routing, dead-letter behavior, session ordering, and the retry policies that protect your system when consumers fail. This guide covers how to test Service Bus locally, in CI,
Testing
Azure Key Vault centralizes secret management, certificate storage, and cryptographic key operations. Testing applications that depend on Key Vault requires careful strategy: you don't want to skip Key Vault in tests (then you're not testing real behavior) but you also can't hardcode production secrets.
Serverless
Azure Functions is Microsoft's serverless compute platform, and like all serverless environments it creates a testing challenge: your code runs inside a host process you don't own, responds to triggers from Azure services, and integrates deeply with the Azure ecosystem. Getting a reliable test suite in
Testing
Azure Cosmos DB is a globally distributed, multi-model database with unique behavior around partition keys, request units (RU/s), consistency levels, and the change feed. Testing these behaviors requires both local emulation and integration tests against the real service. This guide covers both. The Cosmos DB Emulator Microsoft provides
Testing
Azure Container Apps (ACA) is Microsoft's serverless container platform built on Kubernetes and KEDA. It handles scaling, load balancing, and traffic management for you. Testing ACA deployments requires verifying not just that your container runs, but that scaling behaves correctly, revision traffic splitting works, health probes pass, and
Testing
Azure API Management (APIM) sits in front of your backend APIs and handles cross-cutting concerns: authentication, rate limiting, request/response transformation, caching, and routing. Policies are XML rules that execute on every request, and bugs in them break all your APIs simultaneously. Testing APIM policies requires running them locally
Testing
Azure Blob Storage has two testing paths: Azurite for integration tests against a real local emulator, and azure-storage-blob mocks for fast unit tests. Both have sharp edges — Azurite doesn't support all Blob Storage features, and the official SDK's mock story is weaker than AWS&
Azure
Azure Functions testing has a reputation for being awkward. The dependency on function bindings, the ILogger injection pattern, and the mix of trigger types make standard unit testing feel clunky. With the right structure, though, Azure Functions are as testable as any other C# code. Project Structure for Testability The
IoT
AWS IoT Core and Azure IoT Hub are the two dominant managed IoT platforms. Both abstract away the infrastructure complexity, but they introduce new testing challenges: device provisioning flows, message routing rules, device shadows/twins, and serverless processing functions. This guide shows you how to test these integrations without sending