For administrators already managing automation accounts in Delinea, the potential benefit is straightforward: bring those centrally managed credentials into Power Automate’s desktop automation workflow without creating another credential-management island. That is the practical promise—not yet a documented implementation or a reason to start migrating production flows.
What the roadmap covers
The roadmap metadata identifies a specific desktop automation capability:
| Detail | Listed scope |
|---|---|
| Product | Power Automate |
| Platform | Desktop |
| Credential provider | Delinea Secret Server |
| Uses | Machine sign-in and credential retrieval |
| Automation modes | Attended and unattended |
| Cloud scope | Worldwide, Standard Multi-Tenant |
| Status | In development |
| Estimated general availability | March 2027 |
The date is a planning target, not a delivery guarantee. Microsoft explicitly describes its roadmap dates as estimates and says feature information can change. The General Availability release-ring label should therefore not be mistaken for an announcement that the feature is available now.
Why the credential-provider distinction matters
Power Automate already has a credential-management foundation. Microsoft Learn documents Azure Key Vault-backed credentials that can be used in desktop flows or desktop-flow connections. Its documentation distinguishes between credentials used to sign into a machine during runtime and credentials used by actions inside an automation.
That distinction helps explain the Delinea roadmap entry. Starting the automation session and retrieving a password after the flow begins are separate needs. The planned capability explicitly covers machine sign-in as well as credential retrieval, rather than merely describing a way to fetch a secret.
Microsoft’s existing secret-variables action reference documents runtime retrieval for Azure Key Vault and CyberArk credentials, with credential values excluded from logs and credential variables enforced as sensitive. Those are established protections for the documented providers—not confirmation that Delinea will use precisely the same action, configuration, or security behavior.
The likely administrative appeal is less duplication between the organization’s secrets-management system and its automation configuration. Whether the integration delivers that benefit cleanly will depend on its eventual authentication, permissions, and rotation behavior.
Delinea already has an integration—but this is not the same announcement
Delinea’s own documentation describes an existing Power Automate integration package. It includes flows for retrieving secrets and opening an RDP connection using credentials from a retrieved secret, along with configuration components imported into Power Automate as a solution. Power Automate–Secret Server integration is therefore not an entirely new concept.
That package has documented prerequisites: Secret Server 11.x or later and Power Automate installed through the MSI installer. These requirements belong to Delinea’s existing package; they should not be carried over to Microsoft’s planned credential-provider capability without supporting documentation.
The important comparison is scope: Delinea documents a solution-based integration, while Microsoft’s new roadmap entry describes Secret Server as an external credential provider for desktop-flow sign-in and credential retrieval. The evidence does not establish that the forthcoming capability replaces the package or shares its setup requirements.
What administrators should evaluate before deployment
The roadmap description leaves several deployment questions unanswered. A sensible evaluation checklist is:
- Compatibility: Which Secret Server editions, versions, and hosting models are supported?
- Authentication: How does Power Automate authenticate to the vault, and what permissions does it require?
- Secret handling: Can credentials appear in variables, diagnostic output, or run history?
- Lifecycle behavior: What happens after password rotation, credential revocation, or a vault outage?
- Runtime requirements: Do attended and unattended runs have different prerequisites?
- Operations: What audit records, licensing requirements, and troubleshooting tools are provided?
These are acceptance questions, not announced features. Microsoft’s desktop-flow security guidance already recommends credential-based secret handling rather than passing sensitive values into flows as input variables, making it a useful baseline for evaluating the eventual Delinea implementation.
For now, track item 579974 and prepare requirements rather than a deployment plan. The direction is useful for Delinea-backed enterprises, but the implementation details—not the roadmap checkbox—will determine how safely and smoothly it fits into production automation.