Cloud Management Gateway (as CSP)
With 1610, the Cloud Management Gateway feature arrived. Although it's a Pre-Release feature, as Cloud Solution Provider we're UNABLE to use/implement this. And so are our customers...!
When you try to set this up from the ConfigMgr console, a prerequisite is the Azure Management Certificate, which can't be configured as CSP-tenant because this needs the Classic Azure Portal (ASM). This is unacceptable for us, as CSP, as we would have to instruct our customers to get an Azure Subscription separately.
Wesley Droogenbroot
shared this idea
Admindjam
(Product Director, or Executive, Microsoft Endpoint Configuration Manager)
responded
updating to planned.
37 comments
-
Anonymous
commented
When is SCCM 2009 likely to be released?
-
Janek Kröger
commented
In the latest technical preview (2009) we are able to deploy a CMG with virtual machine scale sets in Azure: https://docs.microsoft.com/en-us/mem/configmgr/core/get-started/2020/technical-preview-2009?WT.mc_id=EM-MVP-4034884#bkmk_cmgvmss
Hopefully it doesn't take that long to be merged in the current branch.
-
Anonymous
commented
Bitten by this too. Just the one question to MS, why?
-
Ronni Pedersen
commented
Thank you, Thank you, Thank you!
Denmark has +3500 Microsoft Partners, but only 4 of them can sell EA, so this is a BIG deal, for all Microsoft Partners!
Great News! -
Wesley Droogenbroot
commented
Very exciting news!
-
Samuel Leung
commented
"PLANNED" This is exciting news! Looking forward to more updates about this.
-
Anonymous
commented
@djam any idea when it'll happen?
-
Anonymous
commented
CMG on CSP Please!!!!!
-
Anonymous
commented
come on MS get your skates on
-
Juan Ferreira
commented
Deploy Cloud Management Gateway (CMG) on Azure CSP.
CMG is necessary to configure a service in Azure, called Cloud Services (classic), unfortunately Cloud Services (classic) can't be deployed on Azure CSP. -
Anonymous
commented
This is really a pain and i hope it will be fixed asap!
MFG
Ueli Zimmermann -
TJU
commented
This really should be addressed by making it not rely on classic compute or in some other way. I was surprised to see this still being an issue.
-
Anonymous
commented
Just found this and its nuts. We were on a Microsoft EA but they are pushing us down a CSP. WE have 3k+ people and a multi million azure spend.. Now it sounds like we will need to stand up a single subscription on a credit card. Come on Microsoft
-
Anonymous
commented
Just got bit by this "feature" too. It's a bit disingenuous to say "we support Resource Manager!" when you're still using an underlying deprecated service not available to CSPs. The fact we're going to have to get a single pay-as-you-go subscription to move to the "modern desktop" that Microsoft is touting just isn't right.
-
Kazzan
commented
Really should be addressed. CSP became really growing option to obtain Azure easily and is really unfortunate that CMG does not support this.
-
Alex Durrant
commented
HELLO MICROSOFT - ARE YOU THERE? PLEASE RESPOND TO THIS ISSUE
-
Anonymous
commented
I'm a bit shocked that this was raised in Dec 2016. It really needs some attention, as people have mentioned from the Ignite videos we are told 'go get your Config Manager connected to Azure, do it right now, you are licensed for co-management in Intune'...............but we can't without making things messy.
-
Anonymous
commented
There really, really should be a Microsoft provided workaround document for this.
At Ignite last week there was a huge push for this hybrid management stuff, so it's kind of crazy that this is still an issue after it was brought up at Ignite 2 years ago to the product team.
There are lots of us that run into this issue!
-
Tuna
commented
So until this support is added, what's the work around? Having the business open a Pay-As-You-Go azure instance? Re-sync all of their AD with another instance? That's silly. Either change how ConfigMan uses CMG, or add the Microsoft.ClassicCompute resource to CSP tenants.
-
Mike Garvey
commented
Would really love it if this gets traction. CMG deployment is now done through AzureRM, but yet still uses classic services on the backend?