Skip to content

Conversation

@ferantivero
Copy link
Contributor

Purpose

We wanted to remove the usage of vanilla HttpClient in favor or using The Azure AI Foundry SDK which is a comprehensive toolchain designed to simplify the development of AI applications on Azure

Does this introduce a breaking change?

[ ] Yes [x] No 

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix [x] Feature [ ] Code style update (formatting, local variables) [x] Refactoring (no functional changes, no api changes) [ ] Documentation content changes [ ] Other... Please describe: 

How to Test

TBD

TBD 
  • Test the code
TBD 

What to Check

Verify that the following are valid

  • ...

Other Information

@ferantivero ferantivero changed the title feat (website): [update] start using Azure.AI.OpenAI Foundry SDK feat (refact): [website] start using Azure.AI.OpenAI Foundry SDK Apr 21, 2025
@ferantivero ferantivero force-pushed the feature/419568_website-skd-upd branch from 6fc95fe to 1881772 Compare April 25, 2025 20:55
@ferantivero
Copy link
Contributor Author

The use of the HTTP protocol remains the correct and only viable approach for invoking the Managed Compute /score endpoint where a Flow is getting deployed. No client SDK currently supports real time inference invokes for this type of deployment (not lib available from AI Foundry SDK, or ML SDK, or Prompt flow SDK).

@ferantivero ferantivero deleted the feature/419568_website-skd-upd branch April 25, 2025 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant