it would be nice to have an example on how to change this.

when I compile some code that is using ExceptionTelementry.HandledAt I get the following compiler warning:

'ExceptionTelemetry.HandledAt' is obsolete: 'Use custom properties to report exception handling layer'

but I haven't found any examples for using "custom properties to report exception handling"

I found it is borderline impossible to mock IDocumentClient (CosmosDB) due to the inconsistent implementation of interfaces.

Simple example: IDocumentClient is defined. This is good. IFeedResponse, IResourceResponse are defined. This is good. IDocumentClient returns FeedResponse and ResourceResponse instead of IFeedResponse and IResourceResponse. This is bad. The properties from the concrete implementations that I need to mock are all read-only, so this stymied all my efforts to write any unit tests whatsoever for my storage layer code in my latest project.

Very frustrating to have to search for proper permissions

Azure CLI no longer returns proper return code values on exit, breaking existing devops scripting relying on this (from previous Azure CLI versions). Azure CLI to should return proper return code values in keeping with prior versions.

The Azure Libraries for Java documentation should be enhanced to address all authentication methods, including use of the DelegatedTokenCredentials class.

It's a little disappointing to only be able to target Java 7 & 8 runtime with the provided app service containers. Java 9 and 10 are both GA, 9 more than a year ago now.

Currently, no option is available to create managed encrypted disks while creating encrypted managed volumes using the component "Storage_data_disk" from "azurerm_ virtual_ machine". The option for creating managed encrypted disks should be made available.

The nuget will happily install on any previous .NetFramework version 4.6 and below.

This should have a minimum framework requirement set like other nuget packages.

We are developing a Spring boot Java API that needs to be published to Azure as a Azure API App. However the Azure toolkit is creating a Azure Web App on the Portal. It is not recognizing any Azure API App sites on the App Plan. Since we have a separate Node.js client as a Web App, we need to publish the Sprint boot API as a Azure API App and manage it through the API Gateway/Traffic manager to create a separation of concerns/improved scalability. Please let us know if this option will be available.

We are trying to publish a Spring Boot Java API to Azure as an Azure API App without containerizing the code. The Deployment slots options is not available and it is forcing us to deploy to the Root of the Azure Web App

Whenever I want to import documents with the BulkImport library on CosmosDB, the actual import starts after 1 second.
If i want to import 100 documents, it will take like 1010 ms, when it should be just 10 ms.
The reason for the delay is Task.Delay(***) code in the Microsoft.Azure.CosmosDB.BulkExecutor.CongestionController class.
Can it be removed, or at least, can we have an option to disable this behavior?

Need the following implementation to be present in the IDocumentClient interface for easier compliance of SOLID principles and not having to use dynamic to read the result. Currently it is present only in the concrete class and it is a bad practice to inject concrete dependencies into my repository class.

public Task<DocumentResponse<T>> ReadDocumentAsync<T>(string documentLink, RequestOptions options = null)

Right now the entry point for Azure Fluent API requires dependency on all fluent libraries which is a lot of dependency. It should allow us to have the Azure entry point without all other fluent libraries.

An example of this is, I'm working with ARM and Storage Accounts. ARM's current non fluent .NET library is in Preview so I'm required to used fluent and fluent essentially forces me to include all SDK components which becomes pretty heavy.

why is it with games that xbox owner already own and keeped with in xboxs game library for 360 game and it makes us still pay 4 that i own

When you create a new SQL collection, there is no id(UK) option.

AZ displaying error messages in color is not just pointless but is infuriating.

Try putting these two together...
https://en.wikipedia.org/wiki/Color_blindness
https://www.microsoft.com/en-us/design/inclusive

Many of the .Net Standard (Microsoft.Azure.EventHubs namespace) classes, particularly exceptions, are sealed with internal constructors making unit testing of our error and retry handling impossible or very difficult using hacky workarounds. There should be a way to replicate these exceptions.