Azure 社群支援 | Microsoft Azure

I have noticed that SQL Long term Retention service doesn't show resource group in usage reports. The Instance ID doesn't have a "resourcegroup/****" section, hence the resource group column is blank.It would be helpful to be able to group this instance with a resource group as well. Could you set up an option to specify a resource group when we configure SQL Long term Retention instance?https://docs.microsoft.com/en-us/azure/azure-sql/database/long-term-backup-retention-configureOr, at least make it taggable?

enable to add resource group to SQL Long term Retention instance

I have noticed that SQL Long term Retention service doesn't show resource group in usage reports. The Instance ID doesn't have a "resourcegroup/****" section, hence the resource group column is blank.It would be helpful to be able to group this instance with a resource group as well. Could you set up an option to specify a resource group when we configure SQL Long term Retention instance?https://docs.microsoft.com/en-us/azure/azure-sql/database/long-term-backup-retention-configureOr, at least make it taggable?

Azure activity log missing upn on RBAC assign

specifically the events around Microsoft.Authorization/roleAssignments/write make a few additional API calls to graph.windows.net to contextualize the event further to contain that information natively in AzureActivity? Specifically rather than showing objectid and having the use make manual graph api calls to enrich to find UPN or display name, could this be done in the writing of the logs natively.

2714

票

Make it less expensive to run my very small service on Windows Azure.

2488

票

Continue Azure offering free for Developers

After February 1st 2010, it's going to be tough for developers/freelancers/hobbiest to learn, test and deploy azure applications as it's going to be billed for everything. Like Google AppEngine (http://code.google.com/appengine/whyappengine.html#norisk) Azure should provide free offering for developers with some similar limitations and if the usage goes beyond, one can enter in billing.

1444

票

IIS8 and ASP.NET 4.5 support in AZURE platform

1085

票

Provide hosting in Canada for Canadians to avoid the US Patriot Act

Azure Data Factory (ADF) & Dynamics 365 / CDS Connectors

The option of using Azure Data Factory v2 to migrate data to the Power Platform / CDS / D365 is good, although there are a few features that are missing that almost negate considering the tool as a viable option. Two such examples are:-1. You cannot write to the createdby field on any entity as the createdby is always set in the context of the user in the Linked Service and does not respect the data that is passed to it as part of the Sink data source2. There is no way to migrate data into the native CDS / D365 many-to-many entities (aka mapping table / entity), despite these only consisting of 3 fields (a unique ID and the 2 Foreign Keys of the related entities).3. No support for PartyList type fields

Enable Access Based Enumeration for Azure File Share Service

I would kindly ask you to check and enable the possibility to enable Access Based Enumeration for Azure File Share Service. Currently it is not available but would reflect the possibilities with On-Prem File Servers and File Shares to give the Users a 1:1 User experiance.

Ability to limit access to Azure storage blob for custom error page

When you create a custom error page in Application Gateway, the storage blob stored the error page file needs to be accessible publicly now.It would be nice to be able to limit access to the storage blob so that we can make sure our data is secure.

AADSTS50126: "Invalid username or password" returned even when the password is valid

While trying to log in to Microsoft 365 with OAuth2, some customers are getting this error code, although the username and password is indeed correct.This is because this error code appears to be returned for another error situation which is not related to the password that the user entered.No matter the actual cause of the error, it is crucially important to properly pinpoint the actual cause of the error, so that the software can respond correctly. Different error cases need different responses from the software.From the client software side, the perspective of a client software developer, we must unambiguously distinguish between a) an actually invalid password, where the user entered the wrong password, and b) some technical problem or incompatibility with the domain setup. The reason why it's crucial to differentiate is because the error recovery is very different. In the first case a), I tell the user that his password is wrong and he needs to enter it again. In the second case b), I either do some fallback code or tell the user that I cannot support his account. If I pick the wrong case, because the error code I get is wrong - as in this case -, then I'll keep asking the user to re-enter the passwords, which is completely useless, confusing, and might even lead him to enter other passwords, which is dangerous. In any case, it's a really bad end user experience.The documentation for this error code AADSTS50126 specifically says that this error code means that is an invalid password. However, we see this code when the password is correct, so the error message is flat out wrong. In most configurations, the error code is returned correct, and really only for wrong passwords, but not in all configurations.This causes serious problems for software trying to authenticate, because the software cannot know whether to ask the user to re-enter the password, or use fallback code to use another authentication path.There's no way for us to fix this properly. The bug here is simple: The Microsoft servers return the wrong error code and message. The error message and code are flat out wrong. A MS developer was just re-using the wrong error code, instead of creating a new error code as he should. This must be fixed in the Microsoft software. That's the only place where it can be fixed.This leads to hurt and setup pains for end users. Please fix it.Many people ran into this. Please see comments and more details onhttps://github.com/MicrosoftDocs/azure-docs/issues/30802

提出支援票證

建立事件

了解如何建立 Azure 支援要求

影響新一代的 Microsoft 產品

提供意見反應