I think it's pretty much unanimous that the problems described here with other Azure subscribers trying to deploy the vMX100 that there is indeed an issue with the lock on the named Azure Resource Group.  The result of this deployment cause a "Shadow" Resource Group where the VM for the vMX100 lives.  My suspicion is that even though PowerShell one would run into this probably unless we can isolate just the VMImage deployment via PowerShell.  Deploying the vMX100 from the MarketPlace does so as an application where it's deployment tasks places a lock on the Resource Group almost immediately.  I'll try to create a PowerShell VMImage deployment task now that I have the some time and that the vMX100 is now out of the Beta phase.  I'll report back.   What is so secret about the vMX100 deployment versus the Cisco CSR1000V that requires a lock on the Resource Group?  Cisco felt it necessary to empower Azure subscribers by offering the flexibility to manipulate the Resource Group associated with the CSR1000V.  Why the 180 degree change dealing with this particular vMX100 appliance?  Cisco? ... View more

Wow, literally within in seconds of my posting and it's now available on the Azure Marketplace.  Thanks, this is confirmation of +1 for it's AVAILABLE!!! ... View more

BklynITGuy, I have been working extensively with this particular issue with a client and have formulated two possible paths for them to try. The first is to use the AzureRM PowerShell commands to review VMImage repository for their EastUS region for the availability for their subscription ID access and what they can see publicly. I tried the same AzureRM PowerShell commands with my subscription and although I can see 2 templates they fail to deploy because my Azure subscription hasn't been authorized for the beta program that can only be authorized by a Cisco Meraki representative. The other option I have formulated for the client was to use a Template that I have written and imported on my Azure subscription but again...it fails because I am not authorized to participate in the beta program as per Cisco Meraki. The sad thing is after developing these two possible avenues for this client I am not longer able to get a hold of them to try either of these two approaches. We have tried just about everything for this client to even procure a few MX64 appliances and ask for a trial vMX100 to simulate this clients environment. We went as far as even trying to work different channels to see if we could be late participants to the beta for Cisco Meraki and Azure and they said unfortunately it was closed due to the release date being so close. Anyway, I think your best bet being you do have access to the beta program from Cisco Meraki is to try the AzureRM PowerShell method if you haven't already resolved the issue by other means. ... View more

I just tried today October 31, 2017 and still not available on Azure Marketplace.  This to me sounds like end of October is out and no word on a push into November 2017 timeframe.  This sounds like something is missing or wrong with the beta program to have delayed a release as advertised in multiple announcements to include Cisco and Microsoft announcements.  Maybe there's not enough feedback or active participation within the beta user community or maybe Cisco Meraki could use more Azure user community to have a more complete QA process before launch.  Count me in here as I am not trolling just to ask if/when is the vMX100 ready but I am ready to help with validation on my Azure subscriptions and Meraki Networks. ... View more