none
Action required in view of 'Azure Automation Service Management REST APIs are being retired' RRS feed

  • Question

  • I received a communication on April 18, 2019 that Azure Automation Service Management REST APIs are being retired January 30, 2020.

    I searched for 'management.core.windows.net' and found only that the project .azurePubxml files for 3 classic cloud service projects contain a reference to it as follows:

    <PropertyGroup>{"ServiceManagementEndpoint":"https:\/\/management.core.windows.net\/","ResourceManagementEndpoint":"https:\/\/management.azure.com\/","SubscriptionId":"XXXXb85-bb61-4fe6-b68e-2d8ce41ca06e"}</AzureCredentials>
    ...
    </PropertyGroup>

    I notice that the deprecated ServiceManagementEndpoint is listed together with the recommended ResourceManagementEndpoint. This is a Visual Studio 2015 project and I use it's Publish Azure Application wizard to publish.

    Given that this is the only use of the retired endpoint, do I need to take any action to be able to comply with the April 18th directive and to be able to publish my projects post 01/30/2020?

    Thanks,
    Steve H

    Friday, August 16, 2019 6:02 PM

All replies

  • Classic cloud service projects uses Azure Service Management(ASM) REST API.  So i would suggest you to verify if you are using ASM API's in the projects and migrate cloud service to web apps or virtual machines (according to your requirement) which uses Resource Manager REST API's.

    Hope this helps!

    Wednesday, August 21, 2019 6:00 AM
    Moderator