Hi Harrison, Peter K ,
You are right . Microsoft Purview is supported in South central US , but not in North central US.
Did you try moving ADLS gen2 to South centra US? The issue looks related to region pairing and VNet integration issue between Microsoft Purview and Azure Data Lake Storage Gen2.
When you pick South Central US instead (where Purview lives), it can’t access the data source in North Central US, which might have resulted in the above error. This means Purview's job submission logic isn't finding or handling northcentralus
correctly because PFS doesn't have an endpoint there.
You can go ahead with trying one of the below possibilities:
- Move ADLS to South Central US
- Try disabling Managed VNet on Purview, and allow public network access temporarily (if security allows), then retry profiling.
Hope it helps. Kindly let us know how it goes. Thankyou