Bring Azure-Hosted Models to GitLab Duo
π‘See how to keep AI coding workloads in Azure while mixing models across GitLab Duo features.
β‘ 30-Second TL;DR
What Changed
Connect GitLab Duo Self-Hosted to model deployments running in Microsoft Foundry.
Why It Matters
This integration gives regulated and data-sensitive organizations a practical path to adopt AI coding features without sending source code through an uncontrolled provider endpoint. It also enables workload-specific model selection while consolidating deployment, access, and cost management in Azure.
What To Do Next
Deploy a supported model in Microsoft Foundry and validate its deployment name, model family, Azure permissions, and network path in a GitLab Duo Self-Hosted test environment.
Key Points
- β’Connect GitLab Duo Self-Hosted to model deployments running in Microsoft Foundry.
- β’Assign separate models to agentic workflows, Code Suggestions, and high-volume workloads.
- β’Use Azure region selection, Entra identity, RBAC, network isolation, and Azure Policy for governance.
- β’Verify GitLab's supported-model matrix because Microsoft Foundry's catalog may include unsupported releases.
Weekly AI Recap
Read this week's curated digest of top AI events β
πRelated Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: GitLab Blog β
This is a summary, not the original. Read the source, or get the weekly briefing.
Weekly AI briefing
One email a week. Unsubscribe anytime.