Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

Azure Monitor's Service Map is retiring on September 30th, 2025 #278

Open
azure-deprecation-automation opened this issue Oct 26, 2022 · 1 comment
Labels
area:feature area:api-endpoint All issues related to notices that are applicable to features cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:monitor All notices related to Azure Monitor verified All notices that are verified by an official communication
Milestone

Comments

@azure-deprecation-automation

Azure Monitor's Service Map is retiring on September 30th, 2025

Deprecation ID: 2e5cd350-d587-406b-b576-b9043a4c9216
Deadline: Sep 30, 2025
Impacted Services:

  • Azure Monitor

More information:

Notice

Here's the official report from Microsoft:

On 30 September 2025, Azure Service Map will be retired. To monitor connections between servers, processes, inbound and outbound connection latency, and ports across any TCP-connected architecture, you'll need to migrate to Azure Monitor VM insights.

The map experience of VM insights includes all the same functionality of Service Map, plus:

  • Improved scalability and support for more complex maps.
  • Deeper metrics capabilities for connections.
  • Support for grouping the machines you onboard to the map experience with subscriptions, resource groups, Azure Virtual Machine Scale Sets, and Azure Cloud Services.

Timeline

Phase Date Description
Announcement Oct 07, 2022 Deprecation was announced
Deprecation Sep 30, 2025 Feature will no longer work.

Impact

Azure Monitor's Service Map is retiring on September 30th, 2025 and migration to Azure Monitor VM insights is required.

Required Action

A migration guide is provided here.

Here's the official report from Microsoft:

To continue monitoring processes and dependencies for your Azure virtual machines and on-premises machines, review pricing and migrate to Azure Monitor VM insights by 30 September 2025.

Contact

You can get in touch through the following options:

  • Contact Azure support (link).
  • Get answers from Microsoft Q&A (link).
@azure-deprecation-automation azure-deprecation-automation added area:feature area:api-endpoint All issues related to notices that are applicable to features cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:monitor All notices related to Azure Monitor verified All notices that are verified by an official communication labels Oct 26, 2022
@azure-deprecation-automation azure-deprecation-automation added this to the 2025 milestone Oct 26, 2022
@azure-deprecation-automation
Copy link
Author

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.

@azure-deprecation azure-deprecation locked and limited conversation to collaborators Oct 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:feature area:api-endpoint All issues related to notices that are applicable to features cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:monitor All notices related to Azure Monitor verified All notices that are verified by an official communication
Projects
None yet
Development

No branches or pull requests

1 participant