Close Menu
    Facebook X (Twitter) Instagram
    Trending
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    • Speaking at Modern Endpoint Management Summit 2022
    • Speaking at Nordic Virtual Summit 2022 – 3nd Edition
    • CoLabora Recordings – January 2022
    RONNIPEDERSEN.COM
    • Home
    • Enterprise Mobility
      • Configuration Manager
      • Identity and Access
      • Information Protection
      • Intune
    • Cloud and Data Center
      • Data Center Management
      • Group Policy
      • Enterprise Security
      • Hyper-V
      • PowerShell
    • Guides
    • Webcasts
    • Links
    • About
      • Contact me
      • Disclaimer
    RONNIPEDERSEN.COM
    You are at:Home»Enterprise Mobility»Configuration Manager»SCCM Cloud Management Gateway might fail on new Azure Subscriptions

    SCCM Cloud Management Gateway might fail on new Azure Subscriptions

    10
    By Ronni Pedersen on March 19, 2019 Configuration Manager, Enterprise Mobility

    If you are deploying a Cloud Management Gateway (CMG) in System Center Configuration Manager, and you are using a newly created Azure Subscription, you might see the following error when deploying the CMG:

    Resource Manager – Failed to list keys for storage <name of cmg> with status code: NotFound

    SNAGHTML108870e

    If you then navigate to the Activity log on the Resource Group for the subscription, you can see that the Microsoft.ClassicCompute resource provider is missing.

    image

    This is a recent change (to my knowledge) that will affect all new Azure Subscriptions as the Azure Team has decided that the Microsoft.ClassicCompute will be disabled on all new subscriptions.

    And since the Configuration Manger CMG still requires this uses the Classic Provider, we need to enable it.

    This can be done under “Resource Providers” in the subscription. Just find the Microsoft.ClassicCompute provider, and click Register.

    image

    Delete the failed Cloud Management Gateway, re-create it, and everything should be just fine…

    SNAGHTML10a1f22

    As you can in Azure, the CMG is running as a Classic Cloud Service.

    SNAGHTML10a6b10

    That’s it…

    /Enjoy

    • Tweet
    • Share 0
    • +1
    • LinkedIn 0

    Related

    Ronni Pedersen
    • Website
    • Facebook
    • X (Twitter)
    • LinkedIn

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    Speaking at Nordic Virtual Summit

    Workplace Ninja User Group Denmark February Meetup

    Speaking at Modern Endpoint Management Summit 2022

    10 Comments

    1. Darren on March 19, 2019 23:16

      Can’t believe the timing of this. I’m working through the Microsoft’s Labs on Managing Modern Desktops and had this exact issue as you have to create a new tenant for CMG etc.

      Took me hours to work out the problem and only fixed it yesterday!

      I’m sure this will help many others out there in the community 🙂

      Reply
    2. Pingback: Azure Weekly: March 25, 2019 - Build Azure

    3. Carl Meilleur on April 11, 2019 19:24

      Don’t also Forget that anyone with a CSP subscription won’t even have access to the classic.compute…

      trying to find a timeline to when it’ll be supported

      Reply
      • Ronni Pedersen on July 24, 2019 18:28

        There is no public timeline… I keep asking the Product Group every time I get the chance 🙂

        Reply
        • Tony O on January 7, 2020 19:12

          Have you heard anything on this Ronni? Running up against this for a client as well.

          Reply
    4. Shakti Vaghela on June 1, 2019 08:56

      Thank you for the amazing finding. It helped me with my recent deployment. I also found that, It also required Microsoft.ClassicStorage to be registered. My deployment was failing even after registering the Microsoft.ClassicCompute provider so I did some troubleshooting and found that it also needed Microsoft.ClassicStorage provider.

      Reply
    5. Evan Skillings on June 7, 2019 18:21

      Thanks! This saved me a bunch of time troubleshooting a failed CMG setup.

      I did also have to register Microsoft.Storage as I received a similar error on the second try.

      Going back now I can see that this is listed out on the Microsoft docs-

      The Microsoft.ClassicCompute & Microsoft.Storage resource providers must be registered within the Azure subscription. For more information, see Azure Resource Manager

      https://docs.microsoft.com/en-us/sccm/core/clients/manage/cmg/setup-cloud-management-gateway

      Reply
    6. Johan Falstrup on June 9, 2019 17:52

      I’ve got the exact same error, but the Microsoft.ClassicCompute is already registered. But If I check under the Ressource Groups Activity log I can see the error:

      “The Resource ‘Microsoft.Storage/storageAccounts/”mycloudservice”‘ under resource group ‘”myresourcegroup”‘ was not found.”

      Any idea why?

      Reply
    7. Pingback: New SCCM CMG Setup Guide with Latest EHTTP Certificate #1

    8. ChadsTech on January 25, 2021 15:51

      Thanks for the post. This solved my issue.

      Reply
    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Follow
    APENTO

    Follow APENTO here:

    Subscribe to Blog via Email

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    About
    My name i s Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Endpoint Management and Security, based on Microsoft technologies. I'm also a Microsoft Certified Trainer and a dual Microsoft MVP in both Security and Windows.
    Recent Posts
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    Archives
    TOP POSTS
    • SCCM: Failed to Get Client Identity (80004005)
    • Setting OSDComputerName using CustomSettings.ini
    • How to change the default BitLocker encryption method and cipher strength when using the Enable BitLocker task in ConfigMgr 2007
    • Deploying Office 2016 using the Click-to-Run Deployment Tool
    • Integrate Jamf Pro with Microsoft Intune
    RECENT COMMENTS
    • Sebi on Prepare for Co-Management: Migrate Intune Devices without user affinity
    • Vadim P on SCCM: Failed to Get Client Identity (80004005)
    • TM on Active Directory Based Activation in an multi domain environment
    • unkown on Setting OSDComputerName using CustomSettings.ini
    • TJ Scott on Setting OSDComputerName using CustomSettings.ini
    DISCLAIMER
    The content on this website is presented "as-is" with no guarantees. The use of scripts from this website is at your own risk. Always test before putting something in production! Opinions expressed are my own.
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.