Skip to content

Commit 965ce05

Browse files
priyanshu92Copilot
andauthored
docs: secure Power Pages approvals (#380)
- Keep runtime command approvals enabled by default - Explain credential scope and narrow script allow rules Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
1 parent 7a7ebf5 commit 965ce05

1 file changed

Lines changed: 12 additions & 25 deletions

File tree

plugins/power-pages/README.md

Lines changed: 12 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -465,33 +465,20 @@ A common end-to-end workflow looks like this:
465465
466466
Steps can be run independently — you don't need to follow this exact order. Each skill checks its own prerequisites and will tell you if something is missing. If something goes wrong, `/diagnose-deployment` pattern-matches deployment errors and `/report-issue` opens a pre-filled GitHub issue.
467467

468-
## Running Without Interruption
469-
470-
The plugin invokes multiple tools during a session. To reduce approval prompts:
471-
472-
**Option 1 — Permission mode (recommended)**
473-
474-
```jsonc
475-
// .claude/settings.json
476-
{
477-
"defaultMode": "acceptEdits",
478-
"permissions": {
479-
"allow": [
480-
"Bash(npm run *)",
481-
"Bash(git *)",
482-
"Bash(pac *)",
483-
"Bash(az *)",
484-
"Bash(node *)"
485-
]
486-
}
487-
}
488-
```
468+
## Runtime approvals
489469

490-
**Option 2 — Auto-accept all**
470+
Keep your AI host's runtime approval prompts enabled while using this plugin.
471+
Plugin scripts run on your workstation with the filesystem access and cloud sign-in state available to your user account.
472+
A script that invokes `pac` or `az` may therefore act on Power Platform environments, Dataverse data, and Azure tenants that you can access.
491473

492-
```bash
493-
claude --dangerously-skip-permissions
494-
```
474+
Before approving a command, check the executable, script path, arguments, and target environment.
475+
Pay particular attention to commands that read or change project files, environment configuration, tenant resources, or business data.
476+
Do not grant blanket approval to command families such as `node`, `npm`, `git`, `pac`, or `az`.
477+
478+
If your host supports command-specific allow rules, use them only for an exact plugin script path that you have inspected and expect to run.
479+
Keep approval prompts for commands whose arguments or environment variables select a project, environment, tenant, or data source.
480+
Permission features and rule syntax vary by host and version, so follow the documentation for your host.
481+
Suppressing an approval prompt does not sandbox a script, restrict the programs it can start, or guarantee that the command is safe.
495482

496483
## ALM prompts you may see
497484

0 commit comments

Comments
 (0)