---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Credential handling

# Credential handling {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Extend the workflow engine to manage processes and automate things outside of an
instance with Orchestration. Use the
appropriate credentials required by Orchestration SSH and PowerShell activity
elements: SSH requires SSH and PowerShell requires Windows.

The Cloud Provisioning and Governance application generates credentials (node credentials)
after a VM is provisioned. Node credentials are used to connect to a VM. In addition to node
credentials, the system generates SSH/Windows credentials. These credentials are required for Orchestration, which provides the automation for workflows.

## Pre-existing VMs {#credential-handling__section_u2l_53n_yfb}

Cloud Provisioning and Governance now generates SSH private key credentials and Windows
credentials for all active pre-existing VMs provisioned through Cloud Provisioning and Governance.

## Delete credentials {#credential-handling__section_etp_v3n_yfb}

When you deprovision or delete a VM, all associated credentials are deleted, including the
node credential and SSH private key credentials/Windows credentials, as well as the credentials
alias tag.

## Use the credentials {#credential-handling__section_zkf_1jn_yfb}

See [Use credentials with SSH workflows](https://servicenow-prod.fluidtopics.net/N20Ldapx_vCihwUQCWOiJw "Add an SSH workflow with a credentials tag.") for details.