Thank you for this suggestion! It has been escalated to the Windows Azure engineering team for further evaluation. We will post here to gather additional information as-appropriate.
Great idea. We plan to extend the integration model we have with 3rd party security solutions to any app. No ETA yet.
Daniel Alon, Group Program Manager
Azure Security Center
1,091 votes71 comments · Networking » VPN Connectivity (Point-to-Site, Site-to-Site) · Flag idea as inappropriate… · Admin →
Folks – thanks for you comments on this feature. We understand that this is an important ask for many customers. It is in our list of features to add and is being discussed. Once we decide on a timeline for supporting this we will make an announcement.
I think this decidion will dissapoint a lot of people. Please reconsider this decision
95 votes13 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
Please provide more details. DirectAccess is an on-premises technology and as such may not fall into Azure Active Directory.
You are correct, but the MFA server component support all other scenarios like Citrix, VPN, UAG, etc. and they are also not related to AAD specifically.
Please see my post on the Azure Advisor Yammer: https://www.yammer.com/azureadvisors/#/Threads/show?threadId=384755940&search=directAccess&page=1&style=brief&search_type=following&search_origin=global&trk_search_uuid=61f479f2-3eaa-11e4-aadb-a4badb47279d&trk_event=search_click&trk_result_index=1&trk_entity_model=Message&trk_entity_id=384755940&trk_search_uuid=61f479f2-3eaa-11e4-aadb-a4badb47279d
16 votesunder review · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
I would also be nice if you could configure the specific AV management server as part of the installation like puppet + If you had deployed the AV Management service as part of the subscription where the VM is getting deployed it should be populate as a default.
We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.
After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.
We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.
Thanks for your continued feedback,
-Adam (Azure Billing Team)
You can currently edit the description on runbooks and assets. To do this for runbooks, go to the Configuration page.
On the names, would the ability to add a friendly name (that you can edit at any time) be sufficient or are you hoping to change the workflow name as well?
No current plans but thanks for the suggestion
It should be possible to associate an MSDN accounts with the EA portal to keep track of usage. The EA Admin should be able to assign the MSDN account credits and control usages with limits
We are considering a update service but not specific plans right now. Thanks for the recommendation. Let’s get the votes up. :)