ProPM Agent User Guide
This documentation helps Azure customers use ProPM Agent without mixing daily usage, project administration, platform administration and support diagnostics.
Export PDF
Download the English PDFStart with the right path
| Situation | Open first | Goal |
|---|---|---|
| I am discovering ProPM Agent | Audiences, roles and scopes | Choose the right reading path |
| I need to sign in | Getting started | Access the app and understand empty states |
| I want project status | Dashboard | Read metrics, shortcuts and recent activity |
| I need to select or create a project | Active project | Set the working context |
| I need documents or evidence | Knowledge | Upload, import and search evidence |
| I want to use AI | Agents | Choose an agent, run it and read results |
| I need to review a deliverable | PM Documents | Review, approve, download, publish or add to knowledge |
| I need to audit a run | AI Log | Find the run and effective AI provider |
| I need to handle an alert | Signals and notifications | Read, snooze, dismiss or draft from a signal |
| I need to approve an action | Actions and approvals | Understand approved vs executed |
Paths by profile
| Profile | Main pages |
|---|---|
| Business user | Getting started → Dashboard → Knowledge → Agents → PM Documents |
| Project Manager | Active project → Signals → Actions and approvals → AI Log |
| Project Owner | Access control → Project workspace → Governance → Connectors |
| PMO or leadership | Portfolio → PM Documents → AI Log |
| Azure or tenant administrator | Azure and Entra administration → AI provider → Platform integrations → Licenses, plans and updates |
| Support or audit | Support, audit and diagnostics → AI Log → Maintenance, support and FAQ |
Workflow to remember
The common flow is active project → knowledge → agent → structured output → artifact → PM Document → Download / Publish / Add to knowledge → AI Log.
An agent conversation does not automatically create a final shared document. A PM Document must be reviewed, governed and published or added to knowledge according to project rights and policies.
Essential concepts
| Term | Short definition |
|---|---|
| Active project | Current context for Knowledge, Agents, PM Documents, Signals and AI Log |
| All projects | Scope limited to projects already accessible by the same account |
| Project binding | Link that makes a platform integration usable in a project |
| Structured output | Agent run result, distinct from a final document |
| PM Document | Reviewed, versioned and governed project deliverable |
| Effective AI provider | Provider actually used by a run, visible in AI Log |
| Entitlement | Operational blocker related to license, role, policy, integration or health |
Azure and platform administration
Azure, Entra, AI provider, connector, license and update details are separated from the end-user guide:
| Topic | Page |
|---|---|
| Deploy and finalize access | Azure and Entra administration |
| Configure Save / Validate / Test / Activate | AI provider |
| Define, validate and bind integrations | Platform integrations |
| Manage seats, Marketplace plan and updates | Licenses, plans and updates |
Support
For an incident, provide page URL, active project, time, attempted action, visible message and visible IDs such as Run ID or Trace ID. Never share secrets, keys, tokens or sensitive payloads.