Deploying software across enterprise networks via platforms like Microsoft Intune requires efficient and repeatable methods tailored for IT administrators. When managing Dynamics 365 Field Service, ensuring a seamless setup without user interruption is essential for maintaining productivity. This guide provides a direct path to executing the installation efficiently. By utilizing the verified silent install command, administrators can deploy this package cleanly across target machines while maintaining compliance with all administrative requirements and detection rules.
Quick snapshot: Silently install Dynamics 365 Field Service on Windows
Run in an elevated PowerShell session:
Add-AppxProvisionedPackage -Online -PackagePath "MicrosoftCorporationII.FieldServiceDynamics365_3.26082.6.0_x64__8wekyb3d8bbwe.msix" -DependencyPackagePath "Microsoft.NET.Native.Framework.2.2.appx","Microsoft.NET.Native.Runtime.2.2.appx","Microsoft.UI.Xaml.2.8.appx","Microsoft.VCLibs.140.00.UWPDesktop.appx","Microsoft.VCLibs.140.00.appx" -SkipLicenseOverview
| Application | Dynamics 365 Field Service |
|---|---|
| Version | 3.26052.13.0 |
| Publisher | Microsoft Corp. |
| Installer type | MSIX / Store app |
| Install scope | Machine + User |
| Requires admin | Yes |
| Silent install | Available |
| Silent uninstall | Available |
| Detection method | MSIX package family |
| Installer file | MicrosoftCorporationII.FieldServiceDynamics365_3.26082.6.0_x64__8wekyb3d8bbwe.msix |
Silent install steps
Dynamics 365 Field Service installs through a PowerShell command, so run it in an elevated PowerShell session. Command Prompt cannot run this cmdlet.
Install with PowerShell
- Download or stage the installer (
MicrosoftCorporationII.FieldServiceDynamics365_3.26082.6.0_x64__8wekyb3d8bbwe.msix) to a local folder, for exampleC:\Installers. Place the dependency packagesMicrosoft.NET.Native.Framework.2.2.appx,Microsoft.NET.Native.Runtime.2.2.appx,Microsoft.UI.Xaml.2.8.appx,Microsoft.VCLibs.140.00.UWPDesktop.appx,Microsoft.VCLibs.140.00.appxin the same folder. The install references them via-DependencyPackagePath.
- Open PowerShell as Administrator — right-click Start (or press Win+X), then:
- On Windows 10: choose Windows PowerShell (Admin).
- On Windows 11: choose Terminal (Admin) — it opens Windows Terminal running PowerShell.
- Run the silent install command:
Add-AppxProvisionedPackage -Online -PackagePath "MicrosoftCorporationII.FieldServiceDynamics365_3.26082.6.0_x64__8wekyb3d8bbwe.msix" -DependencyPackagePath "Microsoft.NET.Native.Framework.2.2.appx","Microsoft.NET.Native.Runtime.2.2.appx","Microsoft.UI.Xaml.2.8.appx","Microsoft.VCLibs.140.00.UWPDesktop.appx","Microsoft.VCLibs.140.00.appx" -SkipLicensePS C:\> Set-Location 'C:\Installers'PS C:\Installers> Add-AppxProvisionedPackage -Online -PackagePath "MicrosoftCorporationII.FieldServiceDynamics365_3.26082.6.0_x64__8wekyb3d8bbwe.msix" -DependencyPackagePath "Microsoft.NET.Native.Framework.2.2.appx","Microsoft.NET.Native.Runtime.2.2.appx","Microsoft.UI.Xaml.2.8.appx","Microsoft.VCLibs.140.00.UWPDesktop.appx","Microsoft.VCLibs.140.00.appx" -SkipLicenseInstalling Dynamics 365 Field Service 3.26052.13.0…Installation complete — exit code 0.PS C:\Installers> ▋
Deployment Notes
Key facts to confirm before rolling this out to production machines — permissions required, scope of install, and reboot behavior.
| Requirement | Administrator privileges required |
|---|---|
| Install scope | Machine + User |
| Restart behavior | No restart expected |
Detection Rules
Configure your deployment tool with the detection rule below to confirm a successful install of Dynamics 365 Field Service. The same rule work for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.
MSIX detection
Silent Uninstall Steps
Remove Dynamics 365 Field Service silently from one machine or your entire fleet. The commands below uninstall without prompts and suppress automatic reboots so you control the timing.
Uninstall with PowerShell
Dynamics 365 Field Service is removed through a PowerShell command (Command Prompt cannot run it).
- Open PowerShell as Administrator.
- Run the silent uninstall command.
Get-AppxProvisionedPackage -Online | Where-Object { $_.PackageName -like 'MicrosoftCorporationII.FieldServiceDynamics365_*' } | Remove-AppxProvisionedPackage -OnlineDeployment Examples
Drop the snippet below into your deployment tool, Group Policy, or scheduled task. It wraps the silent install command for Dynamics 365 Field Service as a PowerShell script — copy, save, and run.
PowerShell script example
Save the following content as install-dynamics-365-field-service.ps1 in the same folder as the installer.
Set-Location -Path $PSScriptRoot
$Installer = 'MicrosoftCorporationII.FieldServiceDynamics365_3.26082.6.0_x64__8wekyb3d8bbwe.msix'
Add-AppxProvisionedPackage -Online -PackagePath $Installer -DependencyPackagePath "Microsoft.NET.Native.Framework.2.2.appx","Microsoft.NET.Native.Runtime.2.2.appx","Microsoft.UI.Xaml.2.8.appx","Microsoft.VCLibs.140.00.UWPDesktop.appx","Microsoft.VCLibs.140.00.appx" -SkipLicense
exit $LASTEXITCODEFrequently asked questions
Can I silently install Dynamics 365 Field Service on Windows?
Do I need administrator privileges to install Dynamics 365 Field Service?
Will installing Dynamics 365 Field Service restart the computer?
Add-AppxProvisionedPackage does not trigger a reboot. The package is registered for all users on the next sign-in.How do I verify Dynamics 365 Field Service installed successfully?
How do I silently uninstall Dynamics 365 Field Service?
Remove-AppxProvisionedPackage with the package full name to uninstall Dynamics 365 Field Service.Which deployment tools support these commands?
Troubleshooting
If the install fails, exits with a non-zero code, or leaves no trace on the target machine, work through the checks below. Most issues come down to permissions, paths, or exit code handling.
| Run as administrator | Make sure Command Prompt or PowerShell is opened as Administrator. This installer writes to a machine-wide location and will fail silently without elevated permissions. |
|---|---|
| Verify the installer file name | Confirm that the installer file name matches the command shown in this guide: MicrosoftCorporationII.FieldServiceDynamics365_3.26082.6.0_x64__8wekyb3d8bbwe.msix. |
| Run from the correct folder | Run the command from the folder that contains the installer file. For batch or PowerShell deployments, place the script and installer in the same folder. |
| Check exit codes | If the installer returns a non-zero exit code, review the installer log or your deployment tool's logs. Some packages use additional success exit codes. |
| Restart if required | If the application does not appear immediately after installation, sign out and sign back in, or restart the device — this refreshes Start menu shortcuts, file associations, and Path entries written by the installer. |
| Validate detection rules | If your deployment tool reports the app as not installed, verify that the detection rule matches the installed version, MSI product code, registry key, or file path. Use the Detection Rules section above to confirm whether the application was installed successfully. |
