Formerly known as Azure AI Services or Azure Cognitive Services is a unified collection of prebuilt AI capabilities within the Microsoft Foundry platform
For an Azure AI Search connection in Foundry, the most relevant checks are the connection method, authentication type, and Search-side permissions.
- Recreate the connection from the Foundry portal
- In Microsoft Foundry, make sure New Foundry is on.
- Go to Manage → Project details → Connected resources → Add connection.
- Select Azure AI Search.
- Select the correct Search service and choose the authentication method.
- Confirm the connection appears in Connected resources.
- Prefer Microsoft Entra ID authentication
- Foundry supports different authentication methods depending on connection type.
- Using Microsoft Entra ID can require specific Azure role-based access permissions.
- For keyless authentication, the Foundry account’s system-assigned managed identity must have the required roles on the Azure AI Search service.
- Verify the Azure AI Search endpoint and auth details
- In the Azure portal, open the Azure AI Search service.
- From Overview, confirm the endpoint format is
https://<searchServiceName>.search.windows.net. - If using key-based authentication, go to Settings → Keys, enable Both if needed, and use an admin key.
- Do not store real keys in source control. Use a secure store such as Azure Key Vault.
- If creating the connection by CLI, use the expected payload
For Microsoft Entra ID:
For API key:{ "properties": { "category": "CognitiveSearch", "target": "https://{searchServiceName}.search.windows.net", "authType": "AAD" } }
Then run:{ "properties": { "category": "CognitiveSearch", "target": "https://{searchServiceName}.search.windows.net", "authType": "ApiKey", "credentials": { "key": "{searchAdminKey}" } } }az cognitiveservices account project connection create \ --resource-group <resource-group> \ --name <foundry-resource-name> \ --project-name <project-name> \ --connection-name <connection-name> \ --file connection.json - Important distinction from the Key Vault success
- A successful Key Vault connection does not confirm Azure AI Search permissions are correct.
- Azure AI Search requires its own endpoint and either:
- key-based authentication, or
- keyless authentication with Microsoft Entra ID and RBAC assigned to the project managed identity.
- Most likely next action in this scenario
- Check that the Foundry project managed identity has the required Azure AI Search access for keyless authentication.
- If the portal still returns Service temporarily unavailable, try creating the same connection with Azure CLI using the JSON payload above. That helps confirm whether the issue is portal-side or connection configuration.