Skip to content
| Marketplace
Sign in
Visual Studio Code>Azure>Azure ConnectorsNew to Visual Studio Code? Get it now.
Azure Connectors

Azure Connectors

Microsoft

microsoft.com
|
111 installs
| (0) | Free
Create and manage Connector Namespace connections and trigger configurations from Visual Studio Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Azure Connectors

Create and manage Connector Namespace connections and trigger configurations from Visual Studio Code.

Version 0.1.0 adds official samples discovery and safe, guided sample deployment. Azure Functions connectors and the sample templates are in public preview.

Features

  • Namespace-first manager — select or create a Connector Namespace, then manage its connections and triggers
  • Subscription & Resource Group picker — auto-loads from your Azure CLI session
  • Connector Namespace management — create new namespaces or select existing ones
  • Connector Namespace search — find a namespace by name and reveal it in the Activity Bar tree
  • Dynamic connector discovery from the selected Connector Namespace's Managed API catalog
  • Schema-driven connection settings for OAuth, flat non-OAuth, and authentication-set connectors
  • Collapsible connection cards — keep long connection lists compact by default
  • OAuth consent — opens the authorization page in your browser and verifies connection status
  • Trigger configuration — configure supported connector operations and Function App callbacks
  • Official samples discovery — browse language quickstarts and end-to-end scenarios
  • Guided sample deployment — choose a language and empty local folder; review costs before interactive deployment in a VS Code task terminal

Connector Compatibility

Connector choices are loaded at runtime from the selected Connector Namespace. The extension currently supports connection settings declared as strings, secure strings, integers, booleans, allowed-value lists, OAuth settings, and authentication parameter sets. Connectors with unsupported required settings are blocked with a reason instead of creating an incomplete connection.

The built-in catalog is retained only as a discovery fallback. Trigger operations and their dynamic parameters are loaded from connector Swagger when available. Catalog presence does not guarantee live validation: for example, the service currently returns MQ even though its published managed-connector documentation marks it deprecated. Connectors with unvalidated or partially supported authentication paths may still require environment-specific testing.

Prerequisites

  • Azure CLI installed and authenticated (az login)
  • Target subscription and resource group provisioned
  • For deployed scenarios: compute host with managed identity enabled

Getting Started

  1. Install the extension and sign in to the Azure CLI.
  2. Open Azure Connectors in the Activity Bar, or press Ctrl+Shift+P (Cmd+Shift+P on macOS) and run Azure Connectors: Namespace Manager.
  3. Select an existing Connector Namespace, or create one by selecting a subscription and resource group and entering a namespace name.
  4. In the namespace's Connections & Triggers page, create connections, complete browser OAuth consent where required, and configure triggers and Function App callbacks. Expand the relevant section as needed.
  5. Click a namespace in the tree to open its scoped dashboard. Use Azure Connectors: Search Connector Namespaces to find and reveal namespaces by name, resource group or subscription; refresh the tree after external changes.

Command Palette shortcuts

Press Ctrl+Shift+P and type Azure Connectors:

Command Action
Azure Connectors: Namespace Manager Open namespace selection/creation and connection/trigger management.
Azure Connectors: Open Connector Namespace Open the manager from the palette, or the scoped dashboard when invoked for a tree namespace.
Azure Connectors: Search Connector Namespaces Search and reveal a namespace in the Activity Bar tree.
Azure Connectors: Open Samples Open the official sample index in your browser.
Azure Connectors: Deploy Sample Start the language picker and guided sample deployment.

The empty tree welcome view links to these commands. Open Samples and Deploy Sample also remain available from the view title menu when the tree contains namespaces.

Samples and guided deployment

Browse the official Azure Functions connectors samples (GitHub index). Each language repository contains self-contained apps with its own deployment instructions:

Language Prerequisites and sample instructions
C# (.NET isolated worker) .NET samples · Office 365 Outlook app — .NET 10 SDK
Python Python samples · Office 365 Outlook app — Python 3.13
TypeScript (Node.js) TypeScript samples · Office 365 Outlook app — Node.js 20+ and npm

Before deployment

  • Install a current Azure Developer CLI (azd), Git, Azure CLI 2.75+, and the selected language runtime. Use a current azd release supporting an explicit current-directory initialization target.
  • Install the connector-namespace Azure CLI extension using the instructions linked by the official language samples. Those READMEs document the PowerShell installer and Bash installer; review downloaded scripts before executing them. The VS Code extension does not install these tools or run installer scripts.
  • Deployment hooks require PowerShell 7+ on Windows, or Bash and jq on macOS/Linux.
  • Use an Azure subscription with resource provisioning/access-policy permissions, and an Office 365 test account with permission to consent to Outlook access.
  • Review the selected sample's infrastructure, executable deployment hooks, region availability and prerequisites. Do not assume all languages use the same Connector Namespace region. Configure any required region overrides in the app's azd environment before proceeding with deployment.

Guided workflow

  1. Run Azure Connectors: Deploy Sample in a trusted, local VS Code window. Remote windows are not supported by this flow.
  2. Choose C#, Python, or TypeScript. The guided deployment currently offers the Office 365 Outlook triggers app for each language. Use Open Samples for other connectors and end-to-end scenarios.
  3. Review prerequisites or select Open Sample Instructions. Re-run Deploy Sample when ready.
  4. Choose an existing empty local folder, including no hidden files. The folder is checked again immediately before initialization; files are never intentionally overwritten. Cancel at any picker or confirmation to stop.
  5. Confirm Initialize Sample. A visible task terminal runs azd init --template with the allowlisted language repository URL and an explicit . target. Complete environment prompts in the terminal. This initializes the repository root; the deployable app is in its Office 365 subfolder, not the index/root template.
  6. Inspect the downloaded app's infrastructure and hooks. Only Deploy (May Incur Costs) starts interactive az login, azd auth login, and then azd up from the app subfolder. Each command must succeed before the next starts. Select the app environment, subscription and location in the terminal; the app environment is separate from the initial repository-root environment. No subscription, credentials, consent or CLI prompts are silently accepted.
  7. Complete browser OAuth consent when the sample's deployment hook requests it. Follow the sample README's verification steps, then refresh the Azure Connectors tree and use Search Connector Namespaces to inspect the new namespace.

Costs and data: These samples provision a resource group, Function App/hosting resources, storage, monitoring, identity, Connector Namespace and Outlook connection. They execute downloaded deployment hooks. Email/calendar data may be logged or written to storage; use a test account, avoid sensitive data, and restrict resource access. This is not a cost estimate or a deployment dry run.

Cancellation and failures: Cancelling the cost modal leaves the initialized local files but does not sign in or deploy. Terminate the active task terminal to stop a CLI command. Failed or cancelled initialization/authentication never advances to deployment. A failed or cancelled deployment can leave billable resources. Read the task output; after correcting prerequisites, resume manually from the app folder using its README rather than reinitializing a nonempty target. No files or cloud resources are automatically deleted.

Cleanup: Review the selected app's environment and resources, then manually run azd down --purge from the deployed app folder, as documented by the samples. This deletes resources and data; ensure the environment is correct before confirming. Cleanup is never automatic.

Feedback & Issues

Please file issues and feature requests at the project repository.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft