Breaking Change Policies

API changes will be published to our release notes.

As new functionality is added, we will increment our API version for any non backward compatible changes.

The following are examples of non backward compatible changes:

• Changes to a URL

• Removal, rename, or change to the type of a field

• Removal or rename of APIs or API parameters

• Addition of a required request header or field

The following are examples of backward compatible changes:

• Addition of fields that are nullable or have a default value

• Addition of a member to an enumeration

• Changes to error codes

• Changes to the order of properties

• Changes to the length or format of opaque strings, such as resource IDs