Hi @Yuvaraja P
Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!
It sounds like you're encountering an issue where the new endpoint https://api.purview-service.microsoft.com is redirecting you to the classic portal instead of the new portal, which can be a common issue when transitioning between experiences. Here are some potential causes and solutions for the issue you are experiencing:
- Understand the Changes in Endpoints and Portals:
- Legacy Experience - Users can continue to access the legacy experience of Microsoft Purview at the following URLs: Portal:
web.purview.azure.com
Endpoint:https://[accountname].purview.azure.com/
. - New Experience: The new experience of Microsoft Purview will be available at the following: Portal:
purview.microsoft.com
Endpoint:api.purview-service.microsoft.com
.
- Corporate Network Considerations, ensure your corporate network and security configurations support access to the new Purview experience:
- Update Firewall Rules - You need to verify that your firewall settings allow outbound traffic to the new Purview endpoint api.purview-service.microsoft.com. Your network may be restricted, so ensure your outbound traffic is allowed to these new endpoints.
- Monitor Security and Compliance - Any changes to the network, especially around firewall configurations and access controls, must be monitored to avoid disrupting service.
For more details, please refer: What do I need to prepare before the upgrade and what are some areas of considerations to include in my plan?
I hope this information helps. Please do let us know if you have any further queries.
Thank you.