Azure ML Registry private dns not resolving with private IP

Peter Chaploutskii 20

I have private DNS zone with other Azure ML entries and it's respond with private IP but not <guid>.registry.eastus.api.azureml.ms cname still pointing into public servers "canonical name = vienna-eastus.trafficmanager.net" instead of <guid>.registry.eastus.privatelink.api.azureml.ms. Any issues with private endpoint for ML registry?

Ramr-msft 17,741 Reputation points

2023-11-11T14:12:13.1133333+00:00

Peter Chaploutskii Thanks for the question, We are checking on this and will update on the same.

Giedrius Dambrauskas 0

@Ramr-msft Any updates on this? Same issue occurs in west europe region.

Configuration

Provisioned Azure Machine Learning registry with private endpoint.
Provisioned Azure Machine Learning registry has public network access Disabled.
Private endpoint connected to private DNS zone group privatelink.api.azureml.ms.
Private endpoint and private DNS zone group connected to the same Virtual Network and subnet.
Private endpoint DNS configuration shows DNS record is configured as expected, <Guid>.registry.westeurope.privatelink.api.azureml.ms to IP 10.0.0.100.
Private DNS zone privatelink.api.azureml.ms contains A record <Guid>.registry.westeurope to IP 10.0.0.100.
Virtual Network DNS servers is set to Default (Azure-provided).

Result

When trying to resolve this DNS record from a VM connected to the same Virtual Network, privatelink record resolves to IP address User's image

However, non-privatelink record is not an alias to privatelink endpoint, resolving to public IP address User's image

Possibly due to this, I cannot access a Azure Machine Learning registry content via Azure Machine Learning studio. Whenever I click on either Components, Environments, Models, it just redirects me back to registry overview.

Shouldn't this resoliution be similiar to, for example, key vaults?

User's image

Edit:

After more inspection, I noticed ocasionally I can navigate to Environments and models, but receive the following error in UI:

Failed to fetch environments
Trace ID : 5209e02b-f78e-4484-964c-348dda55754fClient request ID : a0fbe154-e057-493a-b772-93c9700cbd98

And using browser inspect, POST requests to https://ml.azure.com/api/westeurope/ux/v1.0/entities/crossRegion are receiving the following response with 400 status code:

{
    "indexEntitiesResponse": {
        "totalCount": 0,
        "value": [],
        "nextSkip": null,
        "continuationToken": null,
        "entityContainerIdsToEntityContainerMetadata": {},
        "resourcesNotQueriedReasons": {},
        "numberOfEntityContainersNotQueried": null,
        "fanoutData": null,
        "regionalFanoutState": null,
        "shardErrors": null,
        "canSupportSkip": false
    },
    "regionalErrors": {
        "westeurope": {
            "error": {
                "code": "UserError",
                "severity": null,
                "message": "User is not authorized to access provided resources due to none of the workspaces/registries are accessible from outside of the designated private link..",
                "messageFormat": "User is not authorized to access provided resources due to {reason}.",
                "messageParameters": {
                    "reason": "none of the workspaces/registries are accessible from outside of the designated private link."
                },
                "referenceCode": null,
                "detailsUri": null,
                "target": null,
                "details": [],
                "innerError": {
                    "code": "Auth",
                    "innerError": {
                        "code": "Authorization",
                        "innerError": null
                    }
                },
                "debugInfo": null,
                "additionalInfo": null
            },
            "correlation": {
                "operation": "9ce68bc7bfc24a16a37eb85b0a4c3d23",
                "request": "51e8d7e3e3564698"
            },
            "environment": "westeurope",
            "location": "westeurope",
            "time": "2023-12-18T15:58:21.1136563+00:00",
            "componentName": "index",
            "statusCode": 403
        }
    },
    "resourceSkipReasons": {},
    "shardErrors": {},
    "numberOfResourcesNotIncludedInSearch": 0
}

1 answer

Mikhail Chatillon 0 Reputation points Microsoft Employee

2024-11-22T09:02:36.79+00:00

@Ramr-msft @Giedrius Dambrauskas Did you manage to resolve this issue, I am facing a similar situation?
Please sign in to rate this answer.
santoshkc 10,140 Reputation points Microsoft Vendor

2024-11-22T14:15:19.9866667+00:00

Hi @Mikhail Chatillon,

I would recommend creating a new thread on the same forum with as much details about your issue as possible. That would make sure that your issue has better visibility in the community.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure ML Registry private dns not resolving with private IP

1 answer

Your answer