Duplicate subscriptions for a specific resource

Microsoft's current subscription-creation documentation still says duplicate resource and changeType combinations should return 409 Conflict. Your screenshot appears to show matching callRecords resources, change types, and application identifiers, but that alone does not confirm an announced feature change. Compare the complete, unmasked identifiers privately and establish whether the first subscription was still unexpired when the second request succeeded; the screenshot shows different expiration dates. Capture both creation requests, their API versions, timestamps, response statuses, and request IDs, then reproduce with a minimal test in the same tenant. If both subscriptions were simultaneously active with identical relevant settings, raise a Microsoft support case as behavior inconsistent with the documented contract. Do not build production logic around duplicates being accepted until Microsoft clarifies it. Renew an existing subscription through its update operation when that is the objective, and make notification processing tolerant of repeated deliveries.