Multi-Project Portfolio
Unified portfolio view across all active projects with resource allocation optimization, dependency mapping, critical path analysis, and cross-project risk aggregation for MSP-wide visibility.
Unified portfolio view across all active projects with resource allocation optimization, dependency mapping, critical path analysis, and cross-project risk aggregation for MSP-wide visibility.
Within the Projects zone, Multi-Project Portfolio represents a critical operational capability that DevOps AI delivers through its unified platform. This process area operates at HITL Gate Level L1 (Notify), meaning AI executes and notifies the assigned human for review — ensuring visibility while maintaining automation speed.
Multi-Project Portfolio in Practice
DevOps AI implements Multi-Project Portfolio as a fully integrated workflow within the Projects zone. When deployed from the Azure Marketplace, this process area is automatically provisioned with role-appropriate dashboards, notification rules, and automation policies tailored to your MSP's operational requirements.
Workflow Architecture
The Multi-Project Portfolio workflow follows DevOps AI's standard event-driven architecture. Events are ingested through the platform's connector framework — pulling data from PSA tools (ConnectWise, Datto Autotask, HaloPSA), RMM platforms (NinjaRMM, Datto RMM), and Microsoft 365 tenants — then processed through the AI inference pipeline before reaching the L1 gate for automated execution.
Multi-Tenant Isolation
Every operation within Multi-Project Portfolio respects DevOps AI's zero-trust multi-tenant architecture. Client data is isolated at the Azure tenant level, encrypted at rest with customer-managed keys, and processed within geo-fenced compute boundaries. No cross-client data leakage is possible — even AI models are trained on anonymized, aggregated patterns rather than raw client data.
Gate Level L1: Notify
Multi-Project Portfolio is classified at HITL Gate Level L1, which defines exactly when AI acts autonomously and when human judgment is required. This classification was determined through risk analysis of the process area's blast radius, reversibility, and compliance implications.
AI executes autonomously with full logging. No human approval needed.
AI executes and notifies the assigned human for review.
AI prepares and recommends; human must approve before execution.
Humans perform the action with AI decision support only.
Why L1?
Portfolio-level decisions involve resource trade-offs across clients. AI provides optimization recommendations and alerts on conflicts, while project managers retain authority over prioritization.
Platform Integration
Multi-Project Portfolio does not exist in isolation — it integrates with other process areas across the Projects zone and the broader DevOps AI platform through the event mesh architecture. Actions in this process area can trigger workflows in related zones, and events from other zones can feed into Multi-Project Portfolio operations.
Connector Framework
DevOps AI's connector framework provides bi-directional integration with the tools MSPs already use. For Multi-Project Portfolio, this typically includes PSA platforms (ConnectWise Manage, Datto Autotask, HaloPSA), Microsoft Graph API (Azure AD, Intune, Defender), and specialized third-party tools relevant to Projects operations. All connectors are managed through the platform's Marketplace zone — install once, available everywhere.
Analytics & Reporting
Every operation within Multi-Project Portfolio generates structured telemetry that feeds into the Analytics zone. Dashboards provide real-time visibility into process area health, throughput, error rates, and HITL override frequency. Over time, the AI models learn from human overrides to improve future recommendations — creating a continuous improvement loop that makes Multi-Project Portfolio more accurate with every interaction.
Audit Trail
Complete audit provenance is maintained for every action within Multi-Project Portfolio. This includes the triggering event, AI analysis results, HITL gate decisions (including who approved and when), execution outcomes, and any rollback actions. Audit data is immutable, tamper-evident, and exportable in OSCAL format for compliance evidence collection.
All Process Areas in Projects
Explore other process areas within the Projects zone.