Unattended Robotic Process Automation Frequently Asked Questions (FAQs)

• Continuous 24/7 operation ensuring tasks are completed promptly
• Increases efficiency by automating high-volume, repetitive tasks, reducing the likelihood of errors that would occur if completed manually
• Frees up user time by allowing them to focus on more strategic activities of higher value
• Can help manage shared mailboxes, improving communication within NHS organisations

Yes. Please refer to guidance on third-party applications that have been approved on NHS.net Connect.

Yes, once the necessary licences have been acquired, unattended RPA can be used to convert an Excel file to a format suitable for mail merger activities. However, please note that the process needs to be automatable, meaning it should be repetitive in nature.

The NHS.net Connect team assess the core functionality of the platform, including any configurations applied to Power Automate. This assessment does not cover individual workflows or propose specific clinical implementations. Instead, it focusses on ensuring that the platform is reliable, secure, and capable of supporting safe automation in clinical workflows.

If you have attempted to troubleshoot your issue and require further assistance with unattended RPA, please contact your local helpdesk for networking-related issues. For issues related to the platform, environment, licensing, or AI Builder credit allocation, please use the Helpdesk Self-Service (HSS) form.

Unattended RPA is a workflow automation technology that operates independently without human intervention. It is ideal for back-office tasks that require continuous 24/7 operation and the handling of large volumes of data.

Unattended RPA functions by running automation on a designated virtual machine on behalf of a user. The process is managed without human interaction, except for approval flows where the approver acts as a “third party” to the automation. The automation can be triggered automatically by another system or service, or on a set schedule.

If you are a user who would like to utilise unattended RPA within your role, please speak to your Local Administrator or local helpdesk.

Organisations adopting unattended RPA should establish a systematic approach for capturing and prioritising use cases that are requested by internal stakeholders.

Attended RPA requires human interaction to initiate and guide the automation process, typically used for front-office tasks like customer service. Unattended RPA operates independently without human intervention, ideal for back-office tasks that require continuous operation.

Unattended RPA flows are customisable and can be designed to automate various tasks and processes according to your specific business needs, including setting up triggers, and defining actions.

Cloud flows automate processes that connect cloud-based services and applications, while desktop flows automate repetitive tasks on your computer, especially those involving legacy or UI-based applications. More information on creating these flows is available through the following links:

• Create Power Automate Cloud Flows
• Create Power Automate Desktop Flows

Unattended RPA does not require MFA for the automation processes, as they are designed to run independently of human interaction. While owners of flows in Power Platform can log in to make changes to the flows, which requires MFA when logging in as usual with user credentials, they must ensure that MFA is disabled for Application Accounts running unattended flows. This is disabled by default when setting up Application Accounts through NHS.net Connect. To maintain security, it is essential to store your credentials in a secure platform, such as Azure Key Vault, to avoid the risk of exposure. For more information on security and governance, refer to the guidance on Governance for organisations using unattended RPA.

Power Automate Premium is the new Microsoft naming convention for Power Automate Attended RPA. They refer to the same licence when you request to onboard in NHS.net Connect. More information on licencing is available through the Power Automate Licencing Guidance

Please refer to the guidance on Governance for organisations using unattended RPA.

Organisations must ensure that all unattended RPA workflows undergo appropriate DPIAs to ensure compliance and protect personal data. A DPIA must be conducted in order to identify and mitigate potential risks associated with unattended RPA. This assessment should document individuals’ rights and ensure that appropriate safeguards are in place to protect personal data. Additionally, please refer to the guidance on Information Governance Considerations.

Please refer to the following articles for tips on resolving connectivity issues:

• Troubleshoot desktop flows runtime
• Direct connectivity issues in Power Automate for desktop

Please refer to the following articles for tips on resolving error codes encountered during the execution of unattended desktop flows:

• Considerations for unattended automation
• Error code when running desktop flows

Please refer to the “Logon type has not been granted” error when running a desktop flow or creating a connection article if this error occurs.

If your processes stop working, the first step is to check your flow. Here are some troubleshooting suggestions to help you resolve the issue:

• Ensure that the flow is correctly configured and that all necessary settings are in place. Check for any recent changes that might have affected the flow.
• Look for any error messages or logs that can provide insights into what went wrong.
• If the flow involves data extraction or integration, ensure that the data mapping is correct and up to date.
• If your flows are utilising AI Builder credits, check that the consumption has not exceeded the allocated credits and purchase additional credits if necessary.

It is not advisable to use unattended RPA for managing user accounts, as these tasks often require human oversight.

While training is not a pre-requisite to create unattended RPA flows, it is primarily targeted at individuals who are familiar with Microsoft Power Automate. Please consult the Run unattended desktop flows and Overview of unattended automation articles for additional guidance.

Integrating unattended RPA with MFA that uses an authenticator app is not feasible. The security mechanisms involved in MFA, particularly those utilising authenticator apps, are designed to require user input. This user-centric approach ensures that automated systems cannot bypass the authentication process, thereby preserving the integrity and security of the system. Additionally, MFA is often restricted by Data Loss Prevention (DLP) policies within central tenants, further preventing its integration with unattended RPA. Consequently, tasks such as resetting MFA or integrating with the Microsoft Authenticator app cannot be performed using unattended RPA. Please consult the guidance on Multi-Factor Authentication for more information on MFA.