Individual skill

azure-openai-guide

Use OpenAI models on Azure — enterprise deployment with private networking, compliance, and managed scaling.

skills/azure-openai-guide/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
53
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Azure OpenAI Service brings OpenAI's models (GPT, embeddings, and others as
available) into Azure with enterprise controls: private networking, Azure AD
authentication, regional data residency, compliance certifications, and
integration with the Azure ecosystem (APIM, private endpoints, monitoring).
For Microsoft-centric enterprises, it's the sanctioned path to OpenAI-class
models — same model capabilities, Azure's control plane.

The key differences from OpenAI's direct API: deployment-based provisioning
(you deploy named model deployments in your resource), quota management per
deployment, content filtering configurable per use case, and networking that
keeps traffic inside your Azure boundary. The models behave the same; the
operational wrapper is enterprise Azure.