Endpoint resources are no longer supported, and have been migrated to connections. Please delete this resource and re-create it as a connection.

[BarryShehadeh]

ERROR: error executing step command 'provision': deployment failed: error deploying infrastructure: deploying to subscription: Deployment Error Details: ValidationError: Endpoint resources are no longer supported, and have been migrated to connections. Please delete this resource and re-create it as a connection.

while deploying "Azure.ContentSaftey?

[madiepev]

I get the same error when running azd up

[pwine123]

Getting the same error. Any insights into the root cause?

[Xynratron]

Hi,

I run into the same error 30 min ago. Have a look at https://github.com/Azure/azure-dev/issues/3991

There is a merge request, which replaces the endpoint with a connection.

In the bicep file '/infra/core/ai/hub.bicep' (starting at Line 57) replace the resource

  resource contentSafetyDefaultEndpoint 'endpoints' = {
    name: 'Azure.ContentSafety'
    properties: {
      name: 'Azure.ContentSafety'
      endpointType: 'Azure.ContentSafety'
      associatedResourceId: openAi.id
    }
  }

with the following:

  resource contentSafetyConnection 'connections' = {
    name: 'aoai-content-safety-connection'
    properties: {
      category: 'AzureOpenAI'
      authType: 'ApiKey'
      isSharedToAll: true
      target: openAi.properties.endpoints['Content Safety']
      metadata: {
        ApiVersion: '2023-07-01-preview'
        ApiType: 'azure'
        ResourceId: openAi.id
      }
      credentials: {
        key: openAi.listKeys().key1
      }
    }
  }

Hope this helps, still deploying :-)

[pwine123]

@Xynratron - Thank you, that helped resolved the issue.

[nitya]

Hey everyone - sorry for the delay but am catching up with issues now.

1. The move from endpoints to connections-only was a recent change. We have now updated the main branch to move the AOAI connection to make it compliant and the original error should go away.

2. We do need to add a connection based entry for the ContentSafety endpoint - which I am currently testing so expect that to be updated soon. In the interim, the basic RAG sample will still work as expected. The content safety resource is required to explore custom filters etc. and will be added back soon.

There is one pending timing issue that has already been reported (see #139) that we are tracking alongside.

Will close both these once we resolve these pending issues. Thanks for reporting!