How to Connect a Windows VPS to Power Automate Cloud (Fix Entra Join Error)
The Problem
You have Power Automate Desktop working perfectly on your local machine or Hyper-V VM. But the moment you try to connect an Azure VM or any VPS to Power Automate cloud, you hit this error:
Connection failed: [Machine ddeda759-6584-4b73-a32b-f32b513cc64c]
The machine is neither Microsoft Entra nor domain joined.
Correlation id: e6f84b99-3b1c-4f12-8738-b2427cfd95ff
This guide explains exactly why this happens, how to fix it step by step, which VPS provider to choose, and how much RAM you actually need.
Why This Error Happens
Power Automate cloud requires machines running desktop flows to be Microsoft Entra joined (formerly Azure AD joined). This is a security requirement — the cloud service needs to verify the machine belongs to the same Microsoft 365 tenant as your Power Automate license.
Your local Hyper-V setup worked because when you chose "organization" during Windows setup and signed in with your org account, Windows automatically completed the Entra join process. On an Azure VM or third-party VPS, this step must be done manually.
Fix: Join Your VM to Microsoft Entra (Step by Step)
Step 1 — Log Into Your VM
RDP into your Windows VM using a local admin account (not your org account yet). You need local admin access to make the Entra join.
Step 2 — Join the Machine to Microsoft Entra
- Press Windows + I to open Settings
- Go to Accounts → Access work or school
- Click Connect
- Click Join this device to Azure Active Directory (shown as "Join this device to Microsoft Entra ID" on newer Windows)
- Sign in with your Power Automate organization account — the same account linked to your $15/month Premium license
- Follow the prompts and click Join
- Click Done
- Restart the VM
Step 3 — Sign In With Your Org Account After Restart
After the restart, your organization account will appear on the login screen. Sign in with it and complete any MFA prompts.
⚠️ You must now always log into this VM using your org account — not the local account.
Step 4 — Install Power Automate Desktop
- Download Power Automate Desktop with runtime from microsoft.com
- Install it while logged in with your org account
- Open Power Automate Desktop — it should automatically sign you in
- If prompted, sign in with your org account manually
Step 5 — Register the Machine
- In Power Automate Desktop, go to Settings → Machine
- The machine should now register without errors
- Go to make.powerautomate.com
- Navigate to Monitor → Machines
- Your VM should appear in the list
Step 6 — Create the Cloud Connection
- In your cloud flow, add a Run a flow built with Power Automate for desktop action
- When creating the connection, select your registered VM
- Enter your Windows credentials (org account username and password)
- The connection should now succeed
Why Your Local Hyper-V Worked But VPS Didn't
| Setup | Entra Join | Why It Worked |
|---|---|---|
| Local Hyper-V (Windows 10 setup) | ✅ Auto-joined | Choosing "organization" + org account during Windows setup auto-completes Entra join |
| Azure VM (default setup) | ❌ Not joined | Azure VMs provision as standalone machines — Entra join is a manual step |
| Third-party VPS | ❌ Not joined | Same as Azure — Windows installs clean with no org join |
Attended vs Unattended Mode
Since you're using attended mode, your flow runs when a user is actively logged into the VM. This works with a Premium license ($15/month).
Unattended mode — where flows run without anyone logged in — requires an additional Unattended Add-on license on top of your Premium plan. For 24/7 automation where you don't want to keep a session active, unattended mode is worth exploring once your basic setup is working.
Best Cheap Windows VPS Providers for Power Automate
Since you need the VM running 24/7 without keeping your personal machine on, here are the best value providers ranked:
1. Contabo — Best Budget Option ⭐ Recommended
| Spec | Value |
|---|---|
| Price | ~$8.99/month |
| CPU | 4 vCPU |
| RAM | 8GB |
| Storage | 200GB SSD |
| OS | Windows Server 2019/2022 |
Best price-to-performance ratio in this space. Reliable uptime, multiple datacenter locations (US, EU, Asia), no hidden fees. The go-to choice for Power Automate 24/7 setups.
2. Kamatera — Most Flexible
| Spec | Value |
|---|---|
| Price | $4–12/month |
| CPU | Customizable |
| Trial | 30-day free trial |
Pay only for the resources you need. The free trial makes it a risk-free way to test your Power Automate setup before committing.
3. Vultr — Reliable & Fast
| Spec | Value |
|---|---|
| Price | ~$12/month |
| RAM | 2GB (entry) |
| Locations | 25+ globally |
More expensive than Contabo for equivalent specs, but very reliable network performance and a trusted provider.
4. OVHcloud — Enterprise Budget
| Spec | Value |
|---|---|
| Price | ~$10/month |
| RAM | 8GB |
| CPU | 2 vCPU |
Established European provider with solid reliability. Good option if you need EU data residency.
Providers to Avoid
| Provider | Why |
|---|---|
| VPSmart | Poor performance, not worth it |
| Hostinger Windows VPS | Overpriced for specs offered |
| GoDaddy VPS | Poor performance, expensive |
| Any provider under $3/month | Usually unstable for 24/7 workloads |
Verdict: Go with Contabo VPS M at $8.99/month — best value for Power Automate 24/7 automation.
How Much RAM Do You Actually Need?
RAM Breakdown for Power Automate Desktop
| Component | RAM Usage |
|---|---|
| Windows Server 2019/2022 | ~2 GB |
| Power Automate Desktop | ~1 GB |
| Chrome/Edge per instance | ~1–2 GB |
| Background processes | ~0.5 GB |
| Safety buffer | ~1.5 GB |
| Comfortable total | 6–8 GB |
Choose Your RAM Based on Your Flows
4GB — Simple flows only
- No browser automation
- File operations, Excel, API calls
- Very tight budget
- ⚠️ Risk: May struggle during Windows updates
8GB — Recommended for most users ⭐
- Browser automation (web scraping, form filling)
- 2–5 concurrent flows
- 1–2 browser instances
- Reliable 24/7 operation with headroom to grow
12GB+ — Heavy users
- 5+ concurrent flows
- Multiple browser windows simultaneously
- Large Excel file processing
- Enterprise-level workloads
Real-World Example
If your flows open a browser, fill in forms, read/write Excel, and send emails — 8GB is the sweet spot. You'll have comfortable headroom without paying for resources you don't use.
Bottom line: Contabo VPS M with 8GB RAM at $8.99/month covers the vast majority of Power Automate attended automation use cases.
Quick Setup Checklist for a New VPS
- Provision VM with Windows Server 2019 or 2022
- RDP in with local admin account
- Join to Microsoft Entra via Settings → Accounts → Access work or school
- Restart and log in with org account
- Install Power Automate Desktop with runtime
- Register machine in Power Automate Desktop settings
- Verify machine appears in make.powerautomate.com → Monitor → Machines
- Create desktop flow connection in cloud flow
- Test with a simple flow before deploying your full automation
Key Takeaways
- The
"machine is neither Microsoft Entra nor domain joined"error means your VM needs to be manually joined to Entra via Windows Settings - This join must use the same org account linked to your Power Automate Premium license
- Local Hyper-V setups auto-join during Windows setup; Azure VMs and third-party VPS do not
- Contabo VPS M (8GB RAM, $8.99/month) is the best value option for 24/7 Power Automate flows
- 8GB RAM is the recommended minimum for attended flows that include browser automation
- Attended mode works with the $15/month Premium license; unattended requires an additional add-on
Related Topics
- Power Automate Desktop runtime installation guide
- Microsoft Entra ID join vs domain join — what's the difference
- Attended vs unattended desktop flows in Power Automate
- Setting up machine groups in Power Automate cloud
- Windows Server 2022 vs Windows 10 for Power Automate VPS
Still getting the Entra join error after following these steps? Drop the exact error message and your Windows version in the comments.