All tools/Microsoft Power Platform CLI

Microsoft Power Platform CLI

pac

A simple, one-stop developer CLI that empowers developers and ISVs to perform various operations in Microsoft Power Platform.

Detected by pac | macOS, Linux, Windows |learn.microsoft.com

Sync it pac.toml

Sync rules

What travels, what stays, what never leaves

Microsoft Power Platform CLI in your home directory Every rule on this page, by file

· ~/.local/share/Microsoft/PowerAppsCli/authprofiles*.json Never synced

· %LOCALAPPDATA%/Microsoft/PowerAppsCli/authprofiles*.json Never synced

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/pac.tomlThe file this page is generated from

id = "pac"

name = "Microsoft Power Platform CLI"

homepage = "https://learn.microsoft.com/power-platform/developer/cli/introduction"

description = "A simple, one-stop developer CLI that empowers developers and ISVs to perform various operations in Microsoft Power Platform."

# The Power Platform mark, from Microsoft's own Power Platform hub.

icon = "https://learn.microsoft.com/en-us/power-platform/media/hub-page/power-platform.svg"

detect = ["pac"]

# pac keeps no user-written configuration. What it puts in its application

# directory is the auth profiles below, an MSAL token cache, and

# usersettings.json — a generated telemetry uniqueId plus a telemetry on/off

# flag, which belongs to the install rather than to the user.

paths = []

exclude = []

# The auth profiles created by `pac auth create`, which the docs describe as

# "authentication profiles stored on this computer". For a service principal

# profile these carry the applicationId, tenant and client secret; for a user

# profile, the account and environment they authenticate.

# pac itself is closed source, so the paths come from Microsoft's own VS Code

# extension, which watches the files to keep its auth panel in sync —

# src/client/lib/AuthPanelView.ts, `GetAuthProfileWatchPattern()`:

# win32 -> join(LOCALAPPDATA, "Microsoft", "PowerAppsCli"), "authprofiles*.json"

# linux | darwin -> join(HOME, ".local", "share", "Microsoft", "PowerAppsCli"), "authprofiles*.json"

# https://github.com/microsoft/powerplatform-vscode/blob/main/src/client/lib/AuthPanelView.ts

# The same directory is confirmed by that repository's

# src/client/telemetry/localfileusersettings.ts, whose comment reads

# "Application Path and User settings file name should be consistent with CLI".

# The glob is the extension's own: the file has been versioned in place

# (authprofiles.json, then authprofiles_v2.json), and naming one spelling would

# leave the other syncing in the clear.

# Both paths stay literal. macOS does use the dotted spelling, so [dataHome]

# — ~/Library/Application Support there — would be wrong; but [xdgData] is

# wrong too, because it means $XDG_DATA_HOME with ~/.local/share only as its

# default, and the join above takes HOME without consulting the variable. On a

# machine that sets $XDG_DATA_HOME the placeholder would point away from the

# profiles and this rule would stop covering them, which for a credential file

# is the failure that matters.

secret = [

"~/.local/share/Microsoft/PowerAppsCli/authprofiles*.json",

"%LOCALAPPDATA%/Microsoft/PowerAppsCli/authprofiles*.json",

]

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/pac. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these keeps all credential files out.