Skip to content

Desktop Automation That Opens Email Links on a Virtual Machine

Global spirits company

In short

Can Power Automate for desktop open links from emails on a shared virtual machine?

When a team must read an email, find the link inside and open it every time, the work is small but never stops, and it depends on whoever remembers. The client wanted this automated on a machine with only one generic account. We built a desktop flow on a virtual machine that does the whole sequence.

At a glance

  • Email link to browser with no manual steps
  • Five-step Power Automate Desktop flow
  • Runs on one shared generic account

The client

The client is a global spirits company with operations worldwide. The request came from a team that works in Outlook and a web browser on a shared Windows machine.

What it was costing them

  • Repeated manual work: opening the same kind of link from an email, every time one arrives.
  • Delay: the link is only opened when someone notices the email.
  • Key-person risk: the task lives in one person's routine, not in a documented process.
  • No personal account: with one generic account, a normal user-based setup does not fit.

What we built

We built a Power Automate Desktop flow that reads the email, finds the link and opens it, running on a virtual machine.

  • No manual reading: the flow launches Outlook and retrieves the email messages.
  • The right email only: retrieval is filtered so that one email enters the flow.
  • No copy and paste: a text recognition action finds the URL in the email body and stores it in a variable.
  • Straight to the page: the flow launches the browser with that variable.
  • Fits one generic account: a virtual machine hosts the robot, so no person's desktop is needed.
  • Informed run mode: attended and unattended modes were compared before choosing how to start it.

Results

  • Result: the link is opened within a minute of the email arriving instead of when someone next checks.
  • Result: the manual steps of reading, copying and opening the link are removed for each email.
  • The flow has five steps, set out in the working notes.

The risk most teams miss

Desktop flows break when Outlook or a web page changes, and this one assumes one link per email. In month three an email with two links, or a locked virtual machine, stops the process silently. We watch for this with checks for several links, an allow list of sites and an alert when a run fails.

What we would add today

Improvements we would add on top of what is live.

  • Trigger the flow with a cloud flow on new email and run the desktop flow unattended through a machine group.
  • Use the Office 365 Outlook connector where possible, and keep desktop automation for the part with no connector.
  • Add an allow list of link domains before the browser opens anything.
  • Keep the generic account's credentials in Azure Key Vault and monitor runs in a Managed Environment.

Technology

Power Automate Desktop, Outlook, a Windows virtual machine, Microsoft Edge or Chrome.

Tell us which email-driven task your team repeats every day, and we will tell you whether it needs a robot, a cloud flow or both.

Products and capabilities

  • Power Automate for desktop
  • Outlook
  • robotic process automation
  • virtual machine
  • unattended automation

Have a Microsoft project in mind?

Tell us what you need built, fixed or supported. A senior consultant replies within one business day.