windows365
Surface Arc Mouse on iPhone with Windows App — and how to stop your screen from falling asleep mid-session
Picture this: the room you normally use as your home office doubles as the guest bedroom, and right now your guest is fast asleep in there at 7am. But you still need to work. So you grab your iPhone, your Surface Arc Mouse, your Logitech K830 keyboard, fire up the Windows App, mirror everything to the living room TV via AirPlay, and suddenly you have a fully functional Windows desktop from the couch. No laptop needed.
This was my setup this morning. I got my Surface Arc Mouse yesterday, played around with this setup, and already ran into the firmware update process. It works surprisingly well, once you figure out the sleep problem.
Part 1 — Surface mouse on iOS: it’s a preview, but it works
Microsoft quietly added Surface mouse support to the Windows App on iOS. It’s currently in preview, and only specific devices and firmware versions are supported. Let’s go through the setup.
Supported devices
- Surface Mouse
- Surface Arc Mouse
Prerequisites
- iPhone 15 or above with Bluetooth enabled
- A Windows PC with the latest Windows updates installed
- A supported Surface mouse
Step 1 — Firmware update (don’t skip this)
Before anything works, your mouse needs a firmware update. And here’s where Apple fans get a gentle reminder that the world does not always revolve around them — the firmware update can only be done from a Windows PC. Not iPhone. Not iPad. Windows. You’ve been warned.
The required firmware versions and download links for both the Surface Mouse and Surface Arc Mouse are listed in the Microsoft documentation. Run the MSI package in administrator mode on a Windows PC, connect the mouse via Bluetooth, and leave it sitting there for 10 minutes doing absolutely nothing. (Yes, really. Ten minutes. Firmware is not in a hurry.)
Step 2 — Pair with iPhone
Settings → Bluetooth → select the mouse from the list of available devices.Step 3 — Use it in the Windows App
Open the Windows App, start your AVD or Cloud PC session — the mouse is automatically detected. No additional configuration required. You’ll see a proper Windows cursor in your remote session. It genuinely feels like sitting at a desk.
Part 2 — The problem: your iPhone falls asleep
Here’s the catch nobody tells you about. When you’re using a physical mouse and keyboard with your remote session, you’re not touching the iPhone screen. And iOS, in its infinite wisdom, sees zero screen activity — so after your Auto-Lock timeout, the screen dims and locks.
Your AVD session is still alive on the server. But you’re looking at a lock screen. Every. Few. Minutes.
The good news: there are several ways to deal with this. SimplyMac has a solid overview of all options: How to Keep an iPhone from Sleeping. Here are the most practical ones for our AVD use case:
Option A — Move the mouse?
Really, constantly moving the mouse and don’t stop it for more than 30 sec. Guess not …
Option B — Extend Auto-Lock to never or the possible maximum
By default, iOS locks the screen after 30 seconds of inactivity. You can extend this to never or up to the maximum your company has defined if you have an MDM managed device, in my case 5 minutes under Settings > Display & Brightness > Auto-Lock. That buys you more breathing room between interactions, though it does not fully solve the problem for longer sessions where you are heads-down in your remote desktop.
Security note: The longer your Auto-Lock timeout, the longer your phone stays unlocked and accessible if you step away or leave it unattended. In a home setup this is usually fine, but keep it in mind, especially in shared or public spaces.
Option C — Guided Access
iOS Accessibility feature that locks the phone into a single app and can prevent the screen from sleeping. Enable under Settings → Accessibility → Guided Access, then triple-click the side button when the Windows App is open. Slightly more setup, but reliable for longer sessions.
Option D — iOS Shortcuts automation (advanced)
For those who want it fully automatic: you can build a Shortcuts automation that sets Auto-Lock to “the maximum value” when the Windows App opens, and restores your normal setting when it closes. iOS Shortcuts supports app-open and app-close triggers — a neat two-automation setup if you’re comfortable with the Shortcuts app.
Hey Microsoft — one more thing
Until then: mouse around, pick your workaround of choice, and enjoy your living room office setup. The sleeping guest is optional but a good reason to show off with this use case…
Microsoft Teams for Mac on AVD & Windows 365: SlimCore Optimization is Now in Public Preview
If you know me, you know: I’ve been using Mac in my personal life since 2006. Not because I’m an Apple fanboy, but simply because it’s the better tool for me. And if you’re familiar with the EUC world, you also know that hasn’t always been straightforward. macOS has traditionally received new features a little later than Windows. With solutions like Microsoft Azure Virtual Desktop (AVD) or Windows 365, accessing corporate environments from a Mac has become quite solid, and here too, things have improved massively over the last few months.
But when it comes to Microsoft Teams in a VDI environment, Mac users like me have been at a slight disadvantage in recent months. On Windows, Teams optimization with AVD has worked reliably for years. On Mac, however, you were stuck with the older WebRTC-based optimization, missing out on features that Windows users had long enjoyed. That is now changing, starting with a Public Preview.
What’s behind it?
With the new VDI solution for Teams (also referred to as “VDI 2.0”), Microsoft has replaced the existing WebRTC-based optimization with a new media engine called SlimCore, the same engine already powering the native Teams desktop client for Windows. The goal is clear: true feature parity between the native and virtualized Teams client, regardless of the endpoint device.
For Windows endpoints, SlimCore has been generally available since late 2024. Since early 2026, support for macOS endpoints is now in official Public Preview, for AVD and Windows 365 environments.

The official reference: Microsoft 365 Roadmap ID 502524 and the Microsoft Learn documentation for the new VDI solution.
Important: MAU version, not the App Store
There is one key detail here that is easy to miss:
MAU stands for Microsoft AutoUpdate, Microsoft’s update mechanism for macOS apps. The MAU version of the Windows App is obtained directly from Microsoft, not through the App Store. If you have been using the App Store version, you will need to switch to get the new optimization. The minimum required version is Windows App for Mac 11.3.2.
Prerequisites at a glance
| Component | Minimum version |
|---|---|
| Windows App for Mac (MAU version) | 11.3.2 |
| Microsoft Teams in AVD/W365 | 24193.1805.3040.8975 |
Enabling Public Preview: Admin steps
Public Preview is enabled via a Teams Update Policy in the Teams Admin Center, the same mechanism used for all Teams preview features.
... > Settings > About Teams > Early access, enable Public Preview and restart Teams when prompted.
How do I verify the optimization is active?
In the virtualized Teams client, navigate to ... > Settings > About Teams:
AVD SlimCore Media Optimized
New optimization active. All good.
AVD Media Optimized
Legacy WebRTC optimization active. Not yet on SlimCore.
AVD Media not connected
No optimization active.
Newer Teams versions also display a VDI status indicator directly in the top-left corner of the UI, no more digging through settings.
Conclusion
For Mac users in AVD/Windows 365 environments, this is a real step forward. The SlimCore optimization brings features like 1080p video, Gallery View 3×3/7×7, hardware acceleration, and significantly better performance, all things Windows users have known for a while. I’m genuinely pleased to see this finally coming to Mac.
It’s a Public Preview for now, so test it with appropriate expectations. But the direction is right.
Official links
📄 Microsoft Learn: New VDI solution for Teams
🗺️ Microsoft 365 Roadmap: ID 502524
All information in this article is based on publicly available information from Microsoft.
From OnPremises to Cloud – what should it be? A quickstart to the Azure VDIs
Currently, more and more companies are facing the question of whether to continue offering their VDI on‑premises traditionally or whether it should be provided from the cloud in the future.
The EUC world is in transition, and today there are far more serious alternatives than just one or two big, established manufacturers. Or maybe that’s just my personal opinion after stepping out of my bubble a little – but I think there are new needs, and the market is now trying to address them.
I have been a “Citrix tech evangelist” for years, and I am still absolutely convinced of their technology. For me, it’s clear that Citrix has developed the most powerful application and desktop virtualization technologies. However, the competition is catching up, and it doesn’t have to be the ultimate solution for every customer. The company I work for is increasingly focusing on Microsoft and has been pursuing a cloud strategy for years.
It follows naturally that the option to replace on-premises VDIs with a Microsoft Azure VDI solution must be considered.

Some readers of this page may have had the chance in the last two years to hear the presentation by Fabian Tschanz, Stefan Moser, and myself at one of the events (e.g., at the Workplace Ninja Summit or at E2EVC) – they will know that we already ran a project for our developers using Microsoft AVD Single Session as a developer VDI on “greenfield” sites.
Now, things are easy when you start on a greenfield site; however, replacing existing systems becomes difficult due to existing and sometimes unnamed requirements. Sometimes a solution is built for one purpose and then used for something else – something the platform developers didn’t foresee – so it gets lost during migration. So, requirements engineering must be done again here.
Next, we want to cover the following use cases:
- Dedicated VDI for power users with specific needs (usually without company devices) and
- Users of pooled VDIs, who use the VDI occasionally and may also have a company device.
Microsoft offers many solutions, and new variations are still being introduced. So, what is the right choice?

Windows 365? Microsoft Azure Virtual Desktop? And if that’s not enough – there’s also Windows 365 Frontline and/or AVD Multi‑Session. And what is Windows 365 Frontline in Shared Mode?
So, let me try to break this down a bit. When I had to explain On‑Prem, IaaS, PaaS, and SaaS to someone, the pizza model (see image here) helped me, which Albert Barron, Global Principal Architect, Financial Services at Google, explained in a 2014 LinkedIn post.
I wouldn’t claim to be as clever and good at explaining things as Barron, but I’ll try to break down Microsoft Azure VDIs – all the ones mentioned above – into different mixtures of PaaS and SaaS.
Windows 365 Cloud PC
- Fully persistent cloud PC for each user
- Fixed resource allocation (dedicated VM)
- Integrated with Microsoft Endpoint Manager (Intune) for management
- Easy setup without complex infrastructure
🍕In the pizza model, I’d say this is like dining out in a restaurant that always has a place for me – my name is on my dedicated table. I can choose pizzas from the menu in defined sizes. If I provide a recipe, this pizza will be topped and baked according to my wishes.
Windows 365 Frontline Dedicated
- Specifically designed for shift workers or shared usage
- Each user has a dedicated VM that’s only used during working hours
- Licensing based on concurrent usage (not per user)
- Automatic shutdown outside of shift times to save costs
🍕In the pizza model, I’d say this is like dining out in a restaurant where multiple parties share a table alternately – The table is used by three different parties in one day. I can choose pizzas from the menu in defined large sizes. If I provide a recipe, this pizza will be topped and baked according to my wishes.
Windows 365 Frontline Shared
- Multiple users share the same cloud PC
- Specifically for environments with shared workspaces (e.g., call centers)
- Cost-effective usage since no dedicated machine per user is required
- Resources are dynamically allocated
🍕In the pizza model, I’d say this is like dining out in a restaurant where multiple parties share a table alternately – the table is used by three different parties in one day. All parties must eat the same pizza in the same large size. I can choose pizzas from the menu in two defined large sizes. If I provide a recipe, this pizza will be topped and baked according to my wishes.
AVD (Azure Virtual Desktop) Single Session
- Each user has their own VM (similar to Windows 365, but more flexible)
- Support for different VM SKUs (custom performance)
- Management via Azure Resource Manager, not Intune
- Licensing via existing Microsoft 365 licenses or separate Windows licenses
🍕In the pizza model, I’d say this is like dining out in a restaurant that always has space for me – I can decide how the table is set and how big it should be. With pizza, I’m more flexible: it doesn’t have to be round, I can also make it square. If I make a mistake, the pizza gets extremely expensive and I can’t finish it – or it’s so small that I’m still hungry. I can customize the venue and the tables.
AVD (Azure Virtual Desktop) Multi Session
- Multiple users share a single VM (Windows 10/11 Multi Session)
- Ideal for companies with many simultaneous users (e.g., remote workplaces)
- Resources are flexibly shared among users
- More cost-effective than Single Session, as fewer VMs are needed
🍕 Similar to AVD Single Session, but I can let multiple people eat from a single pizza – this way I can efficiently make one pizza. The pizzaiolo only needs to serve one table because we need only one table, but eight people will be full. However, all eight must eat the same type of pizza. I can customize the venue and the tables.
So, what’s the right choice? Well, it really depends on the needs – there’s no wrong solution, maybe the solution just doesn’t fit the problem, aka challenge or use case.
In the coming weeks and months, I will likely be exploring the more flexible solutions with Azure Virtual Desktop in the Single Session and Multi Session variants, and I’m sure I will still face some decisions here…

