Stephane Lapointe
My feedback
-
1 voteStephane Lapointe
shared this idea
·
-
14 votes
Great idea!
Stephane Lapointe
supported this idea
·
-
83 votes
We’ll definitely add this.
Stephane Lapointe
supported this idea
·
-
28 votes
Makes sense. Let us know how important this is for you by voting it up.
Stephane Lapointe
supported this idea
·
-
7 votesunder review · 0 comments · Azure Governance » Azure Resource Graph · Flag idea as inappropriate… · Admin →Stephane Lapointe
supported this idea
·
-
5 votes
An error occurred while saving the comment Stephane Lapointe
supported this idea
·
-
266 votes
We are very excited to announce the Public Preview of Azure Resource Mover https://aka.ms/resource-mover-preview
Azure Resource Mover is a new free service that greatly reduces customer time and effort needed to move resources across regions by providing a built-in dependency analysis, planning, and testing that ensures the resources are prepared to move and then successfully moved to the desired region.
Currently, using this capability, customers can easily move their
Virtual machines with managed disks,
Networking components (NIC, VNET, NSG, Load Balancer, Public IP)
and SQL Azure resources (Database and Elastic pool)from one Azure region to another. The service is available through the Azure portal, PowerShell, and SDKs with any Azure subscription and you can move resources from any public region to any other public region.
We will be improving the resource support coverage in the coming months.
Support for moving customer production workloads is now…
Stephane Lapointe
supported this idea
·
-
65 votesStephane Lapointe
supported this idea
·
-
362 votesStephane Lapointe
supported this idea
·
-
43 votes
We recently published guidance on using Azure Firewall to achieve this for ACI deployments in a Vnet. Would appreciate your feedback on this experience:
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-egress-ip-address
Stephane Lapointe
supported this idea
·
An error occurred while saving the comment Stephane Lapointe
commented
Would like to have a single ip address for both inbound and outbound. It would greatly facilitate ip whitelisting for outbound traffic out of container instances.
-
48 votes
Work is planned for this. In the meantime, we suggest using Azure Firewall as potential work around: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-egress-ip-address
Stephane Lapointe
supported this idea
·
An error occurred while saving the comment Stephane Lapointe
commented
We also need to be able to retrieve a container outgoing IP for white listing purposes
-
2 votesStephane Lapointe
shared this idea
·
-
22 votes2 comments · Azure Resource Manager » Azure Deployment Manager · Flag idea as inappropriate… · Admin →Stephane Lapointe
supported this idea
·
-
10 votesunder review · 0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Stephane Lapointe
supported this idea
·
-
14 votes
Great idea. We can definitely do this.
Stephane Lapointe
supported this idea
·
-
12 votesunder review · 0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Stephane Lapointe
shared this idea
·
-
5 votesStephane Lapointe
supported this idea
·
-
28 votesunder review · 2 comments · Azure Governance » Azure Resource Graph · Flag idea as inappropriate… · Admin →Stephane Lapointe
shared this idea
·
-
1 voteunder review · 1 comment · Azure Governance » Azure Resource Graph · Flag idea as inappropriate… · Admin →Stephane Lapointe
shared this idea
·
-
58 votesStephane Lapointe
shared this idea
·
This would help keep things clean and with best practices. Service Administrator is a very high privilege role, either for Classic or ARM.