Soporte técnico de la comunidad de Azure
Formule preguntas, obtenga respuestas y comuníquese con los ingenieros de Microsoft y los expertos de la comunidad de Azure
Introducción a Azure en Q&A
Obtenga respuestas a sus preguntas técnicas sobre los servicios y productos de Azure. Conéctese con expertos de Microsoft y de la comunidad, comparta sus comentarios y aprenda de otras personas. Azure en Q&A, en el sitio de Microsoft Q&A, va a reemplazar al foro de MSDN. Sin embargo, todavía puede examinar los archivos del foro.
Archivo del foro de MSDN
Respuestas de Microsoft y de la comunidad a preguntas técnicas anteriores de Azure
0
Votos
Change route-based VPN to a policy-based VPN
Forum: Azure Networking (DNS, Traffic Manager, VPN, VNET)
0
Votos
Forum: Azure N-Series Virtual Machines
0
Votos
Forum: Microsoft Azure Site Recovery
0
Votos
User upn changing back and forth between domain aliases
Forum: Azure Active Directory
StackOverflow
Respuestas de la comunidad a las preguntas de desarrollo
207
Votos
Serverfault
Respuestas de la comunidad a las preguntas de administración de Sys/Net
Comentarios de Azure
Publique ideas o sugerencias basas en su experiencia con Azure
Add unmodifiable "createdBy" properties for all resources
If I understand correctly, the recommendation from MSFT is that resources created should be tagged for appropriate information. However this becomes a managed attribute that can be modified. I would find it useful if, during the creation of the resource, the user identity (both Human readable name and UUID) is captured and not modifiable (gets deleted with the resource).This attribute should be query-able from the az command line:az show -n {... "createdByName": "Michael Shire" "createdByUUID": ""...}
Azure policy to block all public access
I would like to be able to create a policy and apply it to subscription(s), that would block any created resource from being able to be reached from the public internet. I want my developers to be able to experiment and try out different resources, but I don't want to put my network at risk while they experiment.Right now I have to play wack-a-mole and identify all the different resources that could get a public IP and create policy around that resource.I believe it would be in Microsoft's best interest to create a policy that one could apply to a subscription to block all public access as a measure of putting security first and not leaving the potential for public exposure of its customers.
Define DWU clearly to do a cost estimation before purchasing.
AWS clearly define its nodes. Please do the same to make the life of Solution Architects easier.This comes all the time as a "Con" in Azure Synapse assessment.
Enable the "Extension" feature for Linux App Services
Enable the "Extension" feature for Linux App Services.More specifically, I need the "Dynatrace Extension" to install OneAgent and monitor my Linux App Services just like I do my Windows App Services.Thank you.
2488
Votos
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.
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
RBAC Role Assignments 2000 limit Constraint
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.
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.