microsoft/Purview GitHub Action

Scan repository files and send to Azure Purview for governance

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None

Inputs

namedescriptionrequireddefault
client-idAzure AD application client ID for OIDC authenticationyes—
client-certificateOptional PEM containing private key + certificate. If provided, certificate auth is used (takes priority over client-secret). If omitted, falls back to client-secret or GitHub OIDC federated credentials.no—
client-secretAzure AD application client secret. If provided (and client-certificate is not), client-secret auth is used. If omitted, falls back to GitHub OIDC federated credentials.no—
tenant-idAzure AD tenant IDyes—
users-json-pathPath to users.json in the workflow-definition repo (relative to repo root). In cross-repo workflows the file is fetched via the GitHub API using state-repo-token.nousers.json
purview-account-nameName of the Purview accountno—
purview-endpointPurview API endpoint URLno—
file-patternsComma-separated file patterns to scan (e.g., "*.md,*.json")no**
exclude-patternsComma-separated file patterns to exclude from scanning (e.g., "node_modules/**,dist/**")no**/.git/**
max-file-sizeMaximum file size in bytes to processno10485760
debugEnable debug loggingnofalse
state-repo-branchBranch in the workflow-definition repo where the state marker is written. If empty, uses that repo's default branch.no""
state-repo-tokenToken (PAT or GitHub App token) with contents write access to the workflow-definition repo. Used for first-run state tracking and for fetching users.json in cross-repo workflows.no""

Outputs

namedescription
processed-filesNumber of files processed
failed-requestsNumber of failed API requests
blocked-filesJSON array of file paths that were blocked by data security policies