Skip to main content
Oximy connects to a Microsoft Foundry project with a project API key and project endpoint. A deployed model becomes available in Sidekick after Oximy confirms that it can stream text and use the tools Sidekick requires.

​
Prerequisites

  • A Microsoft Foundry project with at least one deployed coding model.
  • A project API key.
  • The project endpoint ending in /api/projects/<project-name>.
Verification sends small test requests to check streaming and tool use. Azure may charge for those requests.

​
Connect the project

1

Deploy a coding model

In Microsoft Foundry, deploy the model you want to use. Embedding, image, audio, and other non-coding deployments remain visible only in diagnostics and cannot be selected for a coding task.
2

Copy the endpoint and key

From the deployed model’s Call model panel, copy the project endpoint and API key. Do not paste a deployment-specific URL.
3

Add the provider in Oximy

Open Models → Providers → Add provider, choose Azure, paste the API key and project endpoint, then save.
4

Verify the deployment

Wait for Checking to become Working. Open the deployment details to review any model that was excluded and why.

​
Optional source-IP restriction

Copy every address from Restrict access by IP exactly as displayed and add it to the Azure resource network rules before enforcing default deny. Follow Azure network rules and firewall instructions and the Oximy source-IP guide.

​
Troubleshooting

  • Network blocked: the Azure resource firewall did not allow the request. Add every address currently displayed in Oximy, then run Check now.
  • Authentication rejected: copy a current key from the same project as the endpoint.
  • No deployments discovered: confirm the deployment exists in that project and has finished provisioning.
  • Deployment excluded: open the deployment details. The model must produce text, stream responses, and support the tools required by the selected Harness.