In the 4th bullet on limitations, it says that data explorer is not available from the portal in this setup. Can you let us know what action initiates this limitation? Currently our gen1 ADL has "selected services" turned on and we can still access it via the portal link to data explorer (assuming our IP addresses are whitelisted). Is it by adding a vnet this explorer view becomes unavailable or is it something else? We would like to add a vnet but we need to let our operations people know that data explorer might become unavailable.
Another way of looking at this - as an interim, we'd like to operate the data lake as-is (public endpoint protected by RBAC and whitelists) and also via a private vnet while we test it. Then switch off the public endpoint later.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: c5aad411-3b5f-c08c-b4aa-b109ccc744a1
Version Independent ID: 7f8e6070-b0d5-2a0c-5332-27aef68f7697
In the 4th bullet on limitations, it says that data explorer is not available from the portal in this setup. Can you let us know what action initiates this limitation? Currently our gen1 ADL has "selected services" turned on and we can still access it via the portal link to data explorer (assuming our IP addresses are whitelisted). Is it by adding a vnet this explorer view becomes unavailable or is it something else? We would like to add a vnet but we need to let our operations people know that data explorer might become unavailable.
Another way of looking at this - as an interim, we'd like to operate the data lake as-is (public endpoint protected by RBAC and whitelists) and also via a private vnet while we test it. Then switch off the public endpoint later.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.