Glossary

Glossary

The Locally-specific terms the rest of the documentation uses.

Automatic Configuration

What locally run does: sets the environment variables a tool reads (endpoints, credentials, subscription, CA bundle) so it targets Locally instead of Azure with no change to your code or configuration. More.

Built-in provider

A Resource Provider compiled into the control plane rather than shipped as a plugin - Microsoft.Resources, Microsoft.Authorization, Microsoft.ManagedIdentity and Microsoft.ResourceGraph. Always present; never needs installing.

Data Plane Emulator

The part of Locally that speaks a service's own protocol (Blob REST, AMQP, the Cosmos SQL API) as opposed to the management API that provisions it. List.

Default identity

The service principal locally run authenticates as unless told otherwise. It holds Owner on every seeded subscription and Global Administrator in the directory, so day-one development never meets a 403. Its client ID is stable across launches.

Ephemeral

Gone at shutdown. Everything you provision is, for now.

Installation certificate

A client certificate issued to this install by your Locally Account when you sign in. It carries your plan and is what Locally presents to api.locally.build; it is renewed at least every 32 days and removed by locally logout. Distinct from the local CA and TLS certificate, which secure the endpoints on your machine.

Locally Account

Your sign-in at account.locally.build: plan, installations, and for Team plans the shared runbooks, policies and directory. Optional - without one you get 60-minute sessions, the six core plugins and 3 more of your choice.

Locally region

Locally has its own region names (berlin, not westeurope) so by default a configuration can't target the wrong cloud by accident. Azure's names are available on the Team plan, behind a preview flag. More.

Plugin

One Resource Provider namespace (Microsoft.Storage, Microsoft.KeyVault, …) packaged as its own process, installed into the config directory by locally plugin install and launched by locally build. What you install decides which resource types the control plane serves.

Runbook

Team-shared infrastructure you can replay into a fresh environment: ARM/Bicep templates, database scripts and directory objects, run in order, optionally at every launch. More.

Seeded

Created identically at every launch: the default tenant, your plan's subscriptions, the default identity, and the example directory of users, groups and service principals.

Session

One locally build from start to stop. Sessions have a plan-dependent maximum length, and everything provisioned lives exactly as long as the session.