Duplicate detection & partitioning

In message-based architecture, it's important to be able to handle duplicates to ensure the same message doesn't get processed twice (e.g., a customer doesn't get double-charged). This is especially important when you run applications at scale.

In this exercise, you'll configure duplicate detection in Service Bus and explore partitioning for scale. You'll create one queue with a duplicate detection window, then create a second, partitioned queue. You'll send duplicate messages (same Message Id) to confirm they're filtered within the configured window and inspect the partitioning setting in the portal.