Skip to content

Adding VoyageAI integration documentation - #327

Closed
fzowl wants to merge 2 commits into
MicrosoftDocs:mainfrom
fzowl:voyageai_integration
Closed

Adding VoyageAI integration documentation#327
fzowl wants to merge 2 commits into
MicrosoftDocs:mainfrom
fzowl:voyageai_integration

Conversation

@fzowl

@fzowl fzowl commented Nov 17, 2025

Copy link
Copy Markdown

No description provided.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit e9836b1:

✅ Validation status: passed

File Status Preview URL Details
semantic-kernel/concepts/ai-services/embedding-generation/index.md ✅Succeeded

For more details, please refer to the build report.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit a9a79e7:

💡 Validation status: suggestions

File Status Preview URL Details
semantic-kernel/concepts/ai-services/embedding-generation/index.md 💡Suggestion Details

semantic-kernel/concepts/ai-services/embedding-generation/index.md

  • Line 6, Column 11: [Suggestion: value-deprecated-replace - See documentation] The 'ms.topic: conceptual' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.topic: article'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@markwallace-microsoft

Copy link
Copy Markdown
Contributor

No plans to add VoyageAI to Semantic Kernel

@fzowl

fzowl commented Aug 16, 2026

Copy link
Copy Markdown
Author

Thanks for taking a look, Mark Wallace (@markwallace-microsoft), and for the clear answer. Understood that there are no plans to add a VoyageAI connector to Semantic Kernel — since this PR documents that connector, it doesn't make sense to merge it without the underlying support. Feel free to close it. If the position ever changes, or if there's interest in documenting VoyageAI via the OpenAI-compatible endpoint instead, I'm happy to help. Appreciate your time.

@westey-m

Copy link
Copy Markdown
Contributor

Closing as discussed above.

FYI fzowl, we are now recommending that providers implement the Microsoft.Extensions.AI.Abstractions interfaces. See e.g. https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.ai.iembeddinggenerator-2?view=net-11.0-pp

This also integrates well with e.g. all the Microsoft.Extensions.VectorData implementations.

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.

3 participants