Update migrate-support-matrix-vmware.md#128494
Conversation
Removing the requirements and limitations of agent based dep map since we don't support it
|
Learn Build status updates of commit c702fcf:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/migrate/migrate-support-matrix-vmware.md | Details |
articles/migrate/migrate-support-matrix-vmware.md
- Line 326, Column 237: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/azure-monitor/vm/monitor-vm'. - Line 328, Column 90: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/azure-monitor/vm/vminsights-migrate-from-service-map'. - Line 328, Column 340: [Warning: file-not-found - See documentation]
Invalid file link: 'pricing/details/monitor/'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 822b886: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Hi @prijaisw - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge since the changes aren't extensive, but would you make future content updates in the private repo? Thank you! Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Removes detailed requirements/limitations for agent-based dependency mapping in the VMware support matrix docs and replaces them with guidance pointing readers to agentless dependency analysis and VM Insights.
Changes:
- Deleted the agent-based dependency analysis requirements/limitations tables.
- Added a short note recommending agentless dependency analysis and directing users to Azure Monitor VM Insights.
- Added guidance to migrate from Service Map to VM Insights and clarified pricing implications.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Azure Migrate recommends the use of agentless dependency analysis and no longer provides support for agent based dependency visualization. However, if you still want to use agent-based dependency visualization, you can directly install [Azure Monitor VM Insights](/azure/azure-monitor/vm/monitor-vm) on each server that you want to analyze. | ||
|
|
||
| If you were using ServicMap for agent based dependency analysis, you should migrate from [Service Map](/azure/azure-monitor/vm/vminsights-migrate-from-service-map) to VM Insights as Service Map is retired. Note that agent-based dependency analysis is not free, and Log Analytics workspace usage charges will apply. For pricing details, see [Azure Monitor pricing](/pricing/details/monitor/). |
| @@ -323,31 +323,9 @@ Discovery method | Dependency information between servers is gathered by using | |||
|
|
|||
| ## Dependency analysis requirements (agent-based) | |||
Removing the requirements and limitations of agent based dep map since we don't support it