Tag not monitored by Microsoft.
Hello sysadmin,
Thank you for sharing the detailed steps.
We attempted to reproduce the scenario on our end by creating a custom view and setting it as the favorite view under the Virtual Machines blade. In our testing, the selected view persisted correctly after navigation and reopening the blade.
However, we noticed that the custom view in your case was saved with the name “default.” Since the Virtual Machines blade already has a system-defined default view, using the same name may cause a conflict or prevent the portal from properly retaining the selected favorite view.
To address this, we recommend the following:
Create or rename the custom view with a unique name (for example: “MyVMView”)
Set the newly created/renamed view as the favorite view
Revisit the Virtual Machines blade and verify if the view persists
This approach ensures the portal can clearly distinguish your custom view from the built-in default configuration.
Reference: View and filter Azure resource information
Hope this helps! Please let me know if you have any queries.