提問、獲得解答，以及和 Microsoft 工程師及 Azure 社群專家聯繫
Azure on Q&A 簡介
針對您的 Azure 產品與服務相關技術問題尋找解答。與 Microsoft 和社群專家交流、分享意見反應，並向其他人學習。Microsoft 問與答網站上的 Azure on Q&A 已取代 MSDN 論壇。但您仍可瀏覽論壇封存頁面。
Microsoft 和社群對舊有 Azure 技術問題的回應
Forum: Azure Networking (DNS, Traffic Manager, VPN, VNET)
Forum: Azure N-Series Virtual Machines
Forum: Microsoft Azure Site Recovery
Forum: Azure Active Directory
社群對於 Sys/Net 系統管理問題的回應
根據您的 Azure 使用經驗張貼想法或建議
Currently, we like to replace the Microsoft Customer Agreement on Azure Consumption with a Cloud Solution Provider Agreement. This is only possible for current subscriptions by creating new subscriptions and migrating the current resources to the new subscriptions. Some resources have to be newly created and all the DevOps integration (pipelines, IaC) has to be adapted. We were offered only for the analysis of one subscription/app a couple days of investigation. We estimate for all the subscriptions in place up to a couple of weeks of work. This is a lock-In to MCA and not acceptable. Therefore we ask to implement a way, were the current subscriptions are not touched and just reallocated to the new Agreement.Thank you and kind regardsBenno Richner
Make Azure Tenant logs available for SIEM integration by sending them to an Event Hub.In particular we are interested for logs that indicate subscription creation and deletion.Thank you
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)
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.