Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update azidentity's BREAKING_CHANGES.md #23572

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update azidentity's BREAKING_CHANGES.md #23572

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions sdk/azidentity/BREAKING_CHANGES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# Breaking Changes

## v1.8.0

### New errors from `NewManagedIdentityCredential` in some environments

`NewManagedIdentityCredential` now returns an error when `ManagedIdentityCredentialOptions.ID` is set on a platform whose managed identity API doesn't support user-assigned identities. `ManagedIdentityCredential.GetToken()` formerly logged a warning in these cases. Returning an error instead prevents the credential authenticating an unexpected identity, causing a client to act with unexpected privileges. The affected platforms are:
* Azure Arc
* Azure ML (when a resource ID is specified; client IDs are supported)
* Cloud Shell
* Service Fabric

## v1.6.0

### Behavioral change to `DefaultAzureCredential` in IMDS managed identity scenarios
Expand Down