Support av Azure-communityn

Ställ frågor, få svar och få kontakt med Microsoft-tekniker och experter i Azure-communityn

Introduktion till Azure på Frågor och svar

Få svar på dina tekniska frågor om produkter och tjänster i Azure. Interagera med Microsoft och communityns experter, dela feedback och lär dig av andra. Azure på Frågor och svar, på Microsoft-webbplatsen Frågor och svar, ersätter MSDN-forumet. Du kan dock fortfarande söka i forumarkivet.



    Svar från Microsoft och communityn på äldre tekniska frågor om Azure


    Community-svar på utvecklingsfrågor


    Community-svar på Sys/Net Admin-frågor

    Can I see when an Azure/365 user or device was signed out or shutdown

    • powershell
    • azure
    • microsoft-office-365
    • azure-active-directory
    • microsoft-365

    Monitoring the OnPremise network appliances from Azure?

    • azure
    • monitoring
    • network-monitoring
    • azure-networking
    • system-monitoring

    Feedback om Azure

    Publicera idéer eller förslag baserade på din erfarenhet av Azure

    Allow to disable Subscriptions programmatically

    Neither with Rest nor with Powershell it is possible to disable subscriptions if there are resources in it. But in the portal this is possible without problems. This untraceable behavior is justified with security concerns. But since subscriptions can be "Enabled" again at any time, I think the risk is limited.Therefore I ask you to allow this feature in REST and via cmdlet.

    Extend Front Door Rest API

    Improve Front Door Rest API to allow create/update/delete on the individual components (e.g backend pools, routes) rather than on the entire resource as a whole.We have a case where different teams are creating microsites that use frontdoor as a routing mechanism. Each team wants to IaC their routes and backend pools but cant commit these separately, frontdoor has to be created/updated as a whole. This presents a problem whereby each team need to have insight into the existing routes, pools, etc that other teams have created else they run the risk of deleting all these and only applying their own.As I understand it the Az CLI provides this functionality ( the rest api only allows creation as a whole (

    ARM User interface element VirtualNetworkCombo should provide valid default value

    When creating an Azure Application Template for a Marketplace offer we can use some User Interface element. The User Interface element Microsoft.Network.VirtualNetworkCombo is not using the restriction provided in the element to create the default value proposed to the user. As result the default value generate an error during Validation. Default value should always be valid in my opinion.

    Mangled forum post has mangled content

    Påverka nästa generations Microsoft-produkter

    Lämna feedback