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
Forum: Azure Networking (DNS, Traffic Manager, VPN, VNET)
Forum: Azure N-Series Virtual Machines
Forum: Microsoft Azure Site Recovery
Forum: Azure Active Directory
Community-svar på utvecklingsfrågor
Community-svar på Sys/Net Admin-frågor
Publicera idéer eller förslag baserade på din erfarenhet av Azure
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.
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 (https://docs.microsoft.com/en-us/cli/azure/ext/front-door/network/front-door/backend-pool?view=azure-cli-latest#ext_front_door_az_network_front_door_backend_pool_create)But the rest api only allows creation as a whole (https://docs.microsoft.com/en-us/rest/api/frontdoorservice/frontdoor/frontdoors/createorupdate)
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.
https://azure.microsoft.com/en-us/blog/connecting-to-a-windows-azure-virtual-network-via-a-linux-based-software-vpn-device/ has mangled content
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.
It is very important to us (and the clients we serve) that the hosting platform we use is powered by clean energy (not just offsets).
Please add the options to give access to all reservations, current and future to a group or user. Currently only the user that created the reservation has access to it and you have to grant access on each reservation individually. Very cumbersome and does not allow any automation around reservations. Create a role that will always have access to all reservations.
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.
I have Cisco NGFW VM in backend and which have multiple IP address in his external interface. Which we would like to translate to specific PIP for outbound traffic. But getting error "OutboundRuleCannotBeUsedWithBackendAddressPoolThatIsReferencedBySecondaryIpConfigs" .I read in one of article that this is limitation of ELB but we need this option. This is very basic requirement and important which need by every organization who are planning to move his infra on Azure cloud or already moved.