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


    Respuestas de la comunidad a las preguntas de desarrollo

    How do you get an Access Token from Azure Active Directory that the scaffolded weatherforcast api will accept

    • azure
    • azure-active-directory
    • microsoft-identity-platform

    Local ASP Core 3.1 MVC App with Microsoft Authentication - Single Tenant or Multi Tenant

    • azure
    • azure-active-directory
    • multi-tenant

    Azure B2C One time access to secured API

    • c#
    • azure
    • email
    • azure-ad-b2c
    • one-time-password

    How can I 'listen' for status changes on an azure durable function?

    • azure
    • azure-functions
    • azure-durable-functions


    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.

    Influya en la próxima generación de productos de Microsoft

    Envíanos tus comentarios