Podpora komunity Azure
Ptejte se, získejte odpovědi a spojte se s odborníky z Microsoftu a komunity Azure.
Představujeme Azure na webu Q&A
Najděte si odpovědi na technické dotazy týkající se produktů a služeb Azure. Spojte se odborníky z Microsoftu a komunity, podělte se o zpětnou vazbu a učte se od ostatních. Azure na webu Microsoft Q&A nahrazuje fórum MSDN. Stále však můžete procházet archivy fóra.
Odpovědi Microsoftu a komunity na starší technické dotazy k Azure
Forum: Azure Networking (DNS, Traffic Manager, VPN, VNET)
Forum: Azure N-Series Virtual Machines
Forum: Microsoft Azure Site Recovery
Forum: Azure Active Directory
Odpovědi komunity na dotazy o vývoji
Odpovědi komunity na dotazy o správci systému nebo sítě
Možnost publikovat nápady nebo návrhy na základě zkušeností s Azure
Azure support techs follow up by email or phone. When they follow-up by email, the tech will often dump the email into the support ticket. Maybe this part is even automated, i.e. the email response automatically goes to the ticket as well. The impulse here is good, but the result is near unusable.I've blurred out the details, but as you can see from the attached image, a single message in an already lengthy ticket scrolls off the screen. The email content is being dumped without formatting and without pruning so that the entire history of the email chain is preserved IN EVERY SINGLE MESSAGE.This particular ticket is even worse than normal because there's very little content to begin with, just a very long chain of the support tech replying to their own previous message asking us repeatedly if we'd like to pay for Premium support.Call me old fashioned, but I like my support tickets to always have concise, up-to-date state on the issue at hand. Useless information should be hide-able by any party in there own view. I would also love for the default behaviour of the support techs (and/or their tools) to change from dumping only email correspondence to accurately summarizing the discussion. It's a very useful skill that support people should be practising constantly.For composing entries, I'd suggest something standard like Markdown.See also: https://twitter.com/ccooper/status/1322273129423667200
Currently, we're unable to upload custom greetings to be used for Azure B2C MFA Phone Calls. This feature is enabled in regular Azure AD, but not Azure AD B2C. We'd like this option to be enabled so that when our customers are authenticating to our application, they don't receive a call identified as Microsoft. We'd rather identify the MFA call with our company name.
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.
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
Hello Team,Customer is having high distress in regard to the RBAC Role Assignments 2000 grant limitation. Customer is using Managed Identity and Storage access patterns relying on RBAC grants, it worried customer that it’s a trap and customer will hit that limit in a very short time. These RBAC roles are so useful for the customer but it’s only a matter of time before it hits the limit. Thank you for your consideration.
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.