- enable NPM package link
- hide SDK API docs link as they are not yet available
- add comments on endpoint format
- remove byPage() from example
- Remove sentence from template
## What
- Adds `Managed HSM Crypto Officer` and `Managed HSM Crypto User` role assignments to test user when deploying MHSM.
## Why
Recent RBAC changes for MHSM recently went live which impact how existing permissions are defined. In order to access key operations the Administrator role is no longer sufficient. To keep our tests running we need to add the Crypto Officer and Crypto User role assignments to our test application after the managed HSM is activated.
This PR renames errors `CredentialUnavailable` to `CredentialUnavailableError`, and `AuthenticationRequired` to `AuthenticationRequiredError`, to improve the readability of these exported classes.
I couldn't find any instance of any of our packages using these error names (other than within Identity itself).
Fixes#14662
* Increment package version after release of azure-keyvault-keys
* Increment package version after release of azure-keyvault-secrets
* Increment package version after release of azure-keyvault-certificates
close#13295
Updated README to use `@azure/identity` for authentication rather than `@azure/ms-rest-nodeauth` and `@azure/ms-rest-browserauth`. Made some other miscellaneous tweaks as well to match more closely to the template README.
## What
- If we can remote, and a local crypto operation fails, then we remote the call.
## Why
- In hybrid mode we want to be able to continue supporting crypto operations even if for unknown reasons the local provider fails. This ensures that we can defer to the remote provider if possible.
- In local-only mode, we surface the original error to be handled by user code.
Resolves#14713
* [ai-form-recognizer] Migrate to samples v2
* Move test-assets to assets
* Remove dirname based path computation
* Backport fix for stronglyTypedRecognizedForm to samples/v3
* Fix aka.ms links for FR data types
* Remove old typescript samples
* Use newer invoice sample document
* Rework samples and tag with metadata
* Added package.json metadata
* Fixed a tense inconsistency
* Disable generation of docs.ms metadata until GA.
* Fixed links in sample READMEs
* [min/max] Changed asset path from test-assets to assets
* addressed feedback
The ordering of properties in the XML requests to the Service Bus ATOM API is significant and changing it can have side effects.
In this instance, the ordering issues caused us to appear to have setup forwarding properly for a queue but forwarding was NOT actually enabled. Our previous testing missed this because this data actually round-trips properly through the API but it doesn't trigger whatever actual setting needs to happen to cause forwarding to happen.
This PR reconciles our queue, topic and subscription entities ordering against the .net layer, which acts as the de-facto authority.
Fixes#14539
* Rename common test job files to be consistent with other repos
* Move ci tests into their own file and call via matrix generation job
* Use common platform matrix for ci tests
This PR removes the interface `PersistentCredentialOptions` (introduced in `2.0.0-beta.1`) and instead inlined the options for the persistent cache feature in the options of individual credentials.
Fixes#14502
Reference: https://github.com/Azure/azure-sdk-for-net/pull/18487/
This PR adds the
- [x] FeatureFlag support
- [x] SecretReference support
- [x] Tests for both
- [x] Samples for both
- [x] Changelog
- [x] Links to the samples in the readme
In #14646, we removed the details on different credentials from the top part of the readme. Adding pointer to the new examples file instead. This is very useful instead of making the user scroll to the bottom
## What
- Adds a doc containing multiple snippets for various Identity scenarios
- Adds references to this doc in the README when discussing the credential classes
- Deletes ClientSideUserAuthentication in favor of AzureIdentityExamples
## Why
- While these aren't runnable, these little snippets can provide a good starting point for the various options you can use for credentials. The reference from the README will help folks dig deeper into topics they're interested in
- I noticed that the new doc covers a lot of the same topics that the ClientSideUserAuthentication does so we can centralize
Resolves#14396
This PR removes LocalSupportedAlgorithmName. It is no longer used internally and not needed for customers, so this removes it from the public API and the codebase.
This PR fixes an issue where the original request body is not restored in the event a downstream policy throws and we retry.
This is a small change, and while we plan to migrate to core CAE in the near future this fixes a potential bug in the current release.
Fixes#14590
KarishmaGhiya
Hector Hernandez
Richard Park
Azure SDK Bot
Mike Harder
Jose Manuel Heredia Hidalgo
Jeremy Meng
Maor Leger
Daniel Rodríguez
Vishnu Reddy
Deyaaeldeen Almahallawi
Sarangan Rajamanickam
Will Temple
Orlando Watson
chradek
JoshuaLai
Ramya Rao
Ben Broderick Phillips
Harsha Nalluru
