💡 Intune Weekly Tip – Deploying Win32 apps on ARM64 just got easier! A few months ago, I helped an IT team deploy a Win32 app across hundreds of devices — everything went smoothly… until we hit a wall with ARM64 systems. No matter what we did, those devices just wouldn’t cooperate. It felt like speaking the same language but with a different accent — close, but not compatible. 😅 Now, fast forward to June 2025 — Microsoft Intune finally added ARM64 support for Win32 app deployment. 🎉 Here’s what this means for us: ✅ You can now deploy Win32 apps directly to devices running ARM64 OS. ✅ During the Requirements step, there’s a new option under Operating system architecture for ARM64. ✅ Even existing 64-bit apps will have the ARM64 checkbox selected automatically. ⚠️ Important: After this update, selecting x64 will no longer target ARM64 devices. So if you’ve ever been frustrated trying to deploy Win32 apps to ARM64 hardware — this one’s for you. 🙌 https://lnkd.in/eRQ33pXU DM me "App" and if you would like to try this on your company

Need to automate your applications migration from on prem to Intune but don't have the expertise, or the time? Stuck migrating large (+10Gb) Win32 applications to Intune? Rimo3 has the answer! A customer has been using Rimo3 to consistently migrate many large complex applications, including customized CAD apps, from SCCM to Intune without the need for any external packaging teams or in house expertise, saving days of time and money. Uploading large Win32 apps (over 10GB installers) to Intune is a hugely frustrating process for customers due to frequent timeouts, browser limitations, and inconsistent upload reliability. The Rimo3 platform streamlines this process through automation and bypasses manual uploads and pushes apps directly into Intune, making large app deployment fast, reliable, and hassle-free. Learn more about how we're accelerating the SCCM to Intune migration process here: https://lnkd.in/e_VUftcZ   #Rimo3 #automation #microsoftintune #appmigration

🚀 Windows Autopilot Made Simple – Configuring the Enrollment Status Page (ESP) in Intune Continuing my series on simplifying the Windows Autopilot Enrollment process: 🔹 In earlier posts, I walked through importing the Hardware/Hash ID CSV and creating Deployment Profiles. 🔹 In my latest post, I’ve focused on Enrollment Status Page (ESP) configuration in Intune. The ESP is a critical part of Autopilot as it: ✅ Ensures apps, policies, and configurations are installed before the device is available to the end user ✅ Provides visibility into the provisioning process during OOBE ✅ Helps reduce IT troubleshooting by blocking access until devices are compliant ✅ Delivers a more secure and consistent experience across all enrolled devices Whether you’re an IT admin or just exploring Microsoft Intune + Autopilot, setting up ESP correctly is key to a smooth user experience. I hope this post helps you configure ESP with confidence. Would love to hear your thoughts and feedback! 💬 #MicrosoftIntune #WindowsAutopilot #EndpointManager #DeviceManagement #ModernWorkplace #Intune #ESP

The debate around SCCM vs Intune misses the point entirely. It’s not about “which tool is better.” It’s about how disciplined your packaging is before it even reaches either platform. If your apps are inconsistent, undocumented, and fragile — it doesn’t matter whether you push them via SCCM, Intune, or carrier pigeon. At Algiz, we’ve migrated estates where the packaging process was so clean that the switch to Intune was painless. And we’ve seen others where the migration failed, not because of Intune — but because every package was cobbled together differently. The tool isn’t the weak point. The input is. Fix your packaging discipline, then choose your distribution platform.

I just dropped a new walkthrough on Windows Autopilot + Intune updated for 2025. 💻 It’s honestly one of the biggest time-savers I’ve seen for IT teams and MSPs. 🚀 Here’s what you’ll see: How to completely automate device onboarding with zero touch provisioning Setting up deployment profiles, apps, and security baselines Connecting OneDrive and Defender automatically during OOBE The full end-user experience — from unboxing to productivity in under an hour 🙋 When configured right, Autopilot can save you 1+ hour per device. That’s hundreds of hours per year for growing teams or MSPs doing remote deployments. 🔥 Why this matters: Manual imaging isn’t just slow, it’s inconsistent, unsecure, and unscalable. Autopilot brings order, standardization, and modern management to the endpoint chaos. 🎥 Watch the full video here: https://lnkd.in/gcGH83Cg 📝 Blog recap: https://lnkd.in/gvNZYhQj 👇 How are you handling device provisioning today? Still imaging? Using Autopilot? Something hybrid? Drop your setup in the comments.

🚀 Automating JAMF-style Extension Attributes in Intune with Microsoft Graph API Managing Windows devices in Intune doesn’t natively give us the “Extension Attributes” flexibility we enjoy in JAMF. So I built a framework using Proactive Remediations + Graph API to achieve the same. 🔹 How it works 1️⃣ Graph API App → Secure App Registration with Device.ReadWrite.All. 2️⃣ Detection script → ensures the Remediation script runs every 24 hours. 3️⃣ Remediation script → collects Windows facts (Serial, OS Build, SecureBoot, BitLocker, AV version, etc.). 4️⃣ Script then creates/updates an Entra ID open extension (e.g., com.contoso.inventory). 5️⃣ Every day, devices refresh their attributes. Adding new fields is as simple as editing the payload — no schema migration needed. ✅ Outcome: Now I can track any custom device property (like CrowdStrike/Zscaler versions, Asset Tag, TPM, Secure Boot, etc.) directly in Entra ID, just like JAMF Extension Attributes — but fully automated through Intune + Graph API. #Intune #MicrosoftGraph #EndpointManagement #Automation #AzureAD #EntraID #ModernWorkplace #DeviceManagement #PowerShell #ProactiveRemediations #JAMF #TPM

🚀 Simplifying Application Delivery with MSIX Packaging & App Attach The way we package and deliver applications is evolving rapidly. MSIX, Microsoft’s modern packaging format, is transforming how IT admins handle deployments, updates, and app lifecycle management. 🔹 Why MSIX? ✔ Clean installs & uninstalls (no registry junk) ✔ Secure – digitally signed packages ✔ Delta updates for faster delivery ✔ Works across Intune, SCCM, AVD, and more 🔹 App Attach for Azure Virtual Desktop (AVD) Instead of installing applications into golden images, MSIX App Attach dynamically mounts apps at user login. This means: ⚡ Instant app availability 💾 Reduced storage overhead 🔐 Better separation of apps & OS 🧑💻 Seamless updates by just replacing the VHDX 👉 If you’re working on app packaging, modernization, or AVD, exploring MSIX + App Attach should be on your roadmap. #MSIX #AppAttach #AzureVirtualDesktop #Cloud #ApplicationPackaging #ModernWorkplace

Microsoft to force install the Microsoft 365 Copilot app in October Next month, Microsoft will begin automatically installing the Microsoft 365 Copilot app on Windows devices outside of the EEA region that have the Microsoft 365 desktop client apps. The Microsoft 365 Copilot app integrates the AI-powered Copilot assistant with Microsoft 365 suite apps, including Word, Excel, and PowerPoint, as well as other features like Notebooks and AI agents. Redmond also advised admins to notify their organizations' helpdesk teams and users before the app is forcibly installed on their devices "to reduce confusion and support requests." The rollout will start in early October and be completed by mid-November; however, the Microsoft 365 Copilot app will not be installed on systems within the European Economic Area (EEA). "Starting in October 2025, Microsoft will begin automatically installing the Microsoft 365 Copilot app on Windows devices that have Microsoft 365 desktop client apps," the company said in a Microsoft 365 message center update on Friday. https://lnkd.in/ghbRYcKX

Microsoft is taking Copilot on Windows 11 to a whole new level ⬆️ It’s started testing a feature that lets you share your entire desktop with Copilot. Meaning the AI can see what you see, and chat with you about it in real time. Up until now, Copilot Vision could only look at a single app or window you chose to share. But soon, if you enable it, Copilot will be able to view everything on your desktop at once. Before you panic 😥 this is 100% optional. 
 You must deliberately enter a special mode inside the Copilot app to turn it on. Copilot isn’t peeking at your screen in the background, and it won’t start watching without your say so. Once enabled, here’s what it can do: 👉 Talk you through tasks as you switch between apps
 👉 Offer insights on the content you’re working on
 👉 Guide you step by step through a process in an unfamiliar program
 👉 Even coach you aloud while you’re editing a document or working on a project It won’t click or type for you (at least not yet). But it can highlight areas on screen and say, “Click here next,” or “Try changing this”. Think of it as having a knowledgeable colleague looking over your shoulder… without the awkwardness. Right now, desktop sharing for Copilot Vision is still in testing across Windows Insider Preview channels (Release Preview, Beta, Dev, and Canary). I’m sure it won’t be long till Microsoft rolls it out more widely. Microsoft is clearly betting big on Copilot. With features like Copilot Memory and even customizable personas (yes, you might soon be able to make yours look like Clippy 👀). 💭 What do you think? Would you be happy to share your whole desktop with an AI assistant if it could help you get things done faster?

Microsoft is taking Copilot on Windows 11 to a whole new level ⬆️ It’s started testing a feature that lets you share your entire desktop with Copilot. Meaning the AI can see what you see, and chat with you about it in real time. Up until now, Copilot Vision could only look at a single app or window you chose to share. But soon, if you enable it, Copilot will be able to view everything on your desktop at once. Before you panic 😥 this is 100% optional. 
 You must deliberately enter a special mode inside the Copilot app to turn it on. Copilot isn’t peeking at your screen in the background, and it won’t start watching without your say so. Once enabled, here’s what it can do: 👉 Talk you through tasks as you switch between apps
 👉 Offer insights on the content you’re working on
 👉 Guide you step by step through a process in an unfamiliar program
 👉 Even coach you aloud while you’re editing a document or working on a project It won’t click or type for you (at least not yet). But it can highlight areas on screen and say, “Click here next,” or “Try changing this”. Think of it as having a knowledgeable colleague looking over your shoulder… without the awkwardness. Right now, desktop sharing for Copilot Vision is still in testing across Windows Insider Preview channels (Release Preview, Beta, Dev, and Canary). And for now, it’s only available in the US. I’m sure it won’t be long till Microsoft rolls it out more widely. Microsoft is clearly betting big on Copilot. With features like Copilot Memory and even customisable personas (yes, you might soon be able to make yours look like Clippy 👀). 💭 What do you think? Would you be happy to share your whole desktop with an AI assistant if it could help you get things done faster?