Suporte da Comunidade do Azure
Faça perguntas, receba respostas e ligue-se a engenheiros da Microsoft e a especialistas da comunidade do Azure
Apresentação do Azure on Q&A
Encontre as respostas às suas perguntas técnicas sobre os produtos e serviços do Azure. Ligue-se a especialistas da Microsoft e da comunidade, partilhe comentários e aprenda com outras pessoas. O Azure on Q&A, no site Microsoft Q&A, está a substituir o fórum do MSDN. Mas ainda pode procurar nos arquivos do fórum.
Respostas da Microsoft e da comunidade a perguntas técnicas mais antigas do Azure
Forum: Azure Networking (DNS, Traffic Manager, VPN, VNET)
Forum: Azure N-Series Virtual Machines
Forum: Microsoft Azure Site Recovery
Forum: Azure Active Directory
Respostas da comunidade a questões de desenvolvimento
Respostas da comunidade a questões administrativas de Sys/Net
Publique ideias ou sugestões com base na sua experiência com o Azure
Make Azure AD Premium Free. A lot of our Tenants are having their mailboxes breached. Seems like Azure Premium has good security features that could really help us but it costs too much. This should be free.
Allow other hypervisors to work within the Azure hyper - v environment. VMWare allows hyper - v to work within it's hypervisor, Azure Hyper - v should do the same. I know the development team at Microsoft has figured this out, why can't you folks get your act together and make it available in Azure? We are a multi vendor shop and need this functionality before we migrate all into Azure. You are loosing $$ because of this limitation. If you have this capability please contact me at firstname.lastname@example.org terry
Currently the most granulate scope level is resouce group. It would be helpful if reservations could be scoped to specific virtual machines.
Multiple services can be separated in a subscription by RBAC controls to ensure users/developers of one services resources cannot access another. However support tickets are a subscription wide function which does not fit these controls. Presently all users of a subscription can see, access and amend each others tickets. The suggestion is to bring RBAC controls into subscription support requests so the same separation can be applied to support requests as is applied to Resource Groups and resources to keep different services in a subscription truly separated.
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
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.
I want to transfer a client certificate to the backend with Azure Front Door.However, Azure Front Door doesn't support the SSL passthrough function.I would like to support transferring the client certificate used in the TLS session established between Azure Front Door and the client to the backend.
For now,when customers want to disassociate WAF policy from Application Gateway,we have to change Application Gateway from WAF SKU to Standard SKU.When we changed to Standard SKU,system can be exposed to threats.Please redesign this just like that disassociating WAF policy from listener.