Dominik

cc @navali-msft, @mikekistler

@mikekistler I've filed an issue about the breaking changes policy not being accessible: https://github.com/microsoft/api-guidelines/issues/384 The last manual copy that I own showed adding an optional property as a non-breaking change...

@LuChen-Microsoft What is the new planned release date for this unreleased version, if it's far away from 2023-07-01, should we rename the version?

@memoryhash Email has reached GA in March/April 2023 and the C# SDK lib is now at stable 1.0.0. Announcement blog: https://techcommunity.microsoft.com/t5/azure-communication-services/simpler-faster-azure-communication-services-email-now-generally/ba-p/3788541

@jhendrixMSFT Can you help us override the breaking changes check - for background: the last merge had added repeatability headers for a future api-version. Now they've discovered that they won't...

@glorialimicrosoft Can you please work through the CI issues so that the PR passes the checks? Thanks

**Notes:** * `DELETE /availablePhoneNumbers/reservations/{reservationId}` must delete the reservation so that a GET on reservations won't include it. Alternatively, change to a `POST /availablePhoneNumbers/reservations/{reservationId}/:cancel` to only set the state to cancel....

I like the idea of cross-linking to the SDK API guidelines; this could help with discoverability. "Looking for the SDK API guidelines? You find them here."