Skip to content

Update Foundry CORS proxy endpoint to foundry-cors-proxy#833

Closed
MaanavD wants to merge 2 commits into
microsoft:mainfrom
MaanavD:update-foundry-proxy-endpoint
Closed

Update Foundry CORS proxy endpoint to foundry-cors-proxy#833
MaanavD wants to merge 2 commits into
microsoft:mainfrom
MaanavD:update-foundry-proxy-endpoint

Conversation

@MaanavD

@MaanavD MaanavD commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

What

Repoints the website's model catalog CORS proxy from the old Function App to the newly deployed one:

  • Old: https://onnxruntime-foundry-proxy-hpape7gzf2haesef.eastus-01.azurewebsites.net/api/foundryproxy
  • New: https://foundry-cors-proxy.azurewebsites.net/api/foundryproxy

Why

The proxy was redeployed to a new Azure Function App (foundry-cors-proxy) in an enterprise subscription. The new app is live and serving the same anonymous CORS proxy to the Azure AI Foundry model catalog API.

Changes

  • www/src/routes/models/service.ts — update the hardcoded FOUNDRY_API_ENDPOINT.
  • www/.env.example — update the commented PUBLIC_FOUNDRY_API_ENDPOINT example to match.

Verification

The new endpoint was smoke-tested after deployment:

  • OPTIONS preflight → 200 with CORS headers (Access-Control-Allow-Origin: *, Access-Control-Allow-Methods, Access-Control-Allow-Headers).
  • POST → forwards to Foundry and returns the upstream response verbatim (confirmed the proxy reaches ai.azure.com).

Anonymous access only — no auth token required, consistent with the previous deployment.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

Repoint the website's model catalog proxy from the old onnxruntime-foundry-proxy Function App to the newly deployed foundry-cors-proxy Function App.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 23, 2026 21:22
@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown

@MaanavD is attempting to deploy a commit to the MSFT-AIP Team on Vercel.

A member of the Team first needs to authorize it.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the website's hardcoded CORS proxy endpoint for the Azure AI Foundry model catalog API, repointing it from the old Function App URL to the newly deployed foundry-cors-proxy Function App. It is a simple, low-risk configuration update affecting only the website (www/).

Changes:

  • Update the hardcoded FOUNDRY_API_ENDPOINT constant in the model catalog service.
  • Update the matching commented example for PUBLIC_FOUNDRY_API_ENDPOINT in the env example file.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
www/src/routes/models/service.ts Updates the active FOUNDRY_API_ENDPOINT constant used by the catalog fetch calls to the new proxy URL.
www/.env.example Updates the documentation/example env var to match the new proxy URL.

@MaanavD MaanavD enabled auto-merge (squash) June 25, 2026 18:29
Creates a no-op commit to request a fresh Vercel deployment for PR microsoft#833 without changing source content.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@MaanavD

MaanavD commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator Author

Replaced by #842, which uses an upstream branch instead of a fork branch so Vercel can deploy without the fork authorization gate.

@MaanavD MaanavD closed this Jun 25, 2026
auto-merge was automatically disabled June 25, 2026 19:05

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants