How to Safely Test Microsoft Office 2021 Add-ins Using Windows Sandbox in Windows 11<\/span><\/h2>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/article>\nStep 1: Enable Windows Sandbox Feature<\/b><\/span><\/h3>\nTo enable Sandbox:<\/span><\/p>\n\n- Open the <\/span>Start Menu<\/b>, search for <\/span>Windows Features<\/b>, and select <\/span>Turn Windows features on or off<\/b>.<\/span> <\/li>\n
- In the list, check <\/span>Windows Sandbox<\/b>.<\/span> <\/li>\n
- Click <\/span>OK<\/b>, then restart your computer when prompted.<\/span> <\/li>\n<\/ol>\n
Alternatively, you can run the following from PowerShell as Administrator:<\/span><\/p>\ndism \/online \/Enable-Feature \/FeatureName:”Containers-DisposableClientVM” \/All<\/span><\/p>\nNote: This is for learning purposes only. Type commands manually if needed.<\/span><\/i><\/p>\nStep 2: Create a Sandbox Configuration File<\/b><\/span><\/h3>\nTo customize your sandbox (e.g., to preload Office setup files), create a <\/span>.wsb<\/b> file.<\/span><\/p>\nHere’s a simple example:<\/span><\/p>\n<Configuration><\/span><\/p>\n\u00a0\u00a0<MappedFolders><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0<MappedFolder><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<HostFolder>C:\\SandboxFiles<\/HostFolder><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<ReadOnly>false<\/ReadOnly><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0<\/MappedFolder><\/span><\/p>\n\u00a0\u00a0<\/MappedFolders><\/span><\/p>\n\u00a0\u00a0<LogonCommand><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0<Command>cmd.exe<\/Command><\/span><\/p>\n\u00a0\u00a0<\/LogonCommand><\/span><\/p>\n<\/Configuration><\/span><\/p>\n <\/p>\n
Save this as <\/span>OfficeTest.wsb<\/span> on your desktop. Replace <\/span>C:\\SandboxFiles<\/span> with the folder where your Office installer and add-in files are located.<\/span><\/p>\nStep 3: Prepare Installation Files<\/b><\/span><\/h3>\nBefore launching the sandbox:<\/span><\/p>\n\n- Place your <\/span>Office 2021 Pro Plus installer<\/b> and any plugins or add-ins you want to test inside the folder specified in your .wsb file (e.g., <\/span>C:\\SandboxFiles<\/span>).<\/span> <\/li>\n
- Also include:<\/span> \n
\n- Plugin documentation<\/span> <\/li>\n
- Any required configuration files<\/span> <\/li>\n
- Dependency libraries (for COM or VSTO plugins)<\/span> <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
Step 4: Launch the Sandbox<\/b><\/span><\/h3>\n\n- Double-click the <\/span>.wsb<\/span> file you created.<\/span> <\/li>\n
- A new temporary Windows environment will boot up.<\/span> <\/li>\n
- Navigate to your mapped folder (e.g., <\/span>C:\\Users\\WDAGUtilityAccount\\Desktop\\SandboxFiles<\/span>).<\/span> <\/li>\n
- Run the Office 2021 installer.<\/span> <\/li>\n<\/ol>\n
Follow standard installation steps. Once Office is installed, you can begin plugin testing.<\/span><\/p>\nStep 5: Install and Test Your Add-ins<\/b><\/span><\/h3>\nFor Office Web Add-ins (JavaScript)<\/b><\/span><\/h4>\n\n- Open an Office app (e.g., Word).<\/span> <\/li>\n
- Go to <\/span>Insert > Get Add-ins > My Add-ins > Shared Folder<\/b>.<\/span> <\/li>\n
- Point to a manifest XML file stored in your mapped folder.<\/span> <\/li>\n<\/ol>\n
For COM or VSTO Plugins<\/b><\/span><\/h4>\n\n- Run the installer or manually register the DLL using the following command:<\/span> <\/li>\n<\/ol>\n
regsvr32 “C:\\Path\\To\\Your\\Plugin.dll”<\/span><\/p>\n\n- Launch the relevant Office application.<\/span> <\/li>\n
- The plugin should appear in the <\/span>Add-ins<\/b> tab.<\/span> <\/li>\n<\/ol>\n
Monitor how it behaves:<\/span><\/p>\n\n- Does it load correctly?<\/span> <\/li>\n
- Are there script errors?<\/span> <\/li>\n
- Is there a UI conflict?<\/span> <\/li>\n
- How does it interact with the Ribbon or task pane?<\/span> <\/li>\n<\/ul>\n
Step 6: Test for Conflicts or Performance Issues<\/b><\/span><\/h3>\nUse Office functions and features while the add-in is enabled. Pay attention to:<\/span><\/p>\n\n- Load time of Office apps<\/span> <\/li>\n
- Crashes or freezing<\/span> <\/li>\n
- Interference with other features<\/span> <\/li>\n
- Network activity if applicable (for API-driven add-ins)<\/span> <\/li>\n<\/ul>\n
You can also test scenarios like:<\/span><\/p>\n\n- File open\/save with plugin active<\/span> <\/li>\n
- Clipboard operations<\/span> <\/li>\n
- Undo\/redo with plugin commands<\/span> <\/li>\n
- Authentication flows (if the add-in connects to cloud services)<\/span> <\/li>\n<\/ul>\n
Step 7: Document Your Results<\/b><\/span><\/h3>\nBefore closing the sandbox, record:<\/span><\/p>\n\n- Success or failure to load the add-in<\/span> <\/li>\n
- Any error messages or logs<\/span> <\/li>\n
- Screenshots if UI issues are found<\/span> <\/li>\n
- Impact on Office performance<\/span> <\/li>\n<\/ul>\n
This helps with debugging or QA reporting.<\/span><\/p>\nImportant: Once the sandbox is closed, all data is wiped. Be sure to save documentation to your mapped folder if needed.<\/span><\/i><\/p>\nStep 8: Reset and Repeat<\/b><\/span><\/h3>\nOne of the biggest advantages of Sandbox is repeatability:<\/span><\/p>\n\n- Close the sandbox window<\/span> <\/li>\n
- Make changes to your add-in or environment (e.g., new plugin version)<\/span> <\/li>\n
- Re-launch the <\/span>.wsb<\/span> configuration file<\/span> <\/li>\n<\/ul>\n
You\u2019re now testing on a fresh Windows install again.<\/span><\/p>\nTroubleshooting Tips<\/b><\/span><\/h2>\n
Step 1: Enable Windows Sandbox Feature<\/b><\/span><\/h3>\nTo enable Sandbox:<\/span><\/p>\n\n- Open the <\/span>Start Menu<\/b>, search for <\/span>Windows Features<\/b>, and select <\/span>Turn Windows features on or off<\/b>.<\/span> <\/li>\n
- In the list, check <\/span>Windows Sandbox<\/b>.<\/span> <\/li>\n
- Click <\/span>OK<\/b>, then restart your computer when prompted.<\/span> <\/li>\n<\/ol>\n
Alternatively, you can run the following from PowerShell as Administrator:<\/span><\/p>\ndism \/online \/Enable-Feature \/FeatureName:”Containers-DisposableClientVM” \/All<\/span><\/p>\nNote: This is for learning purposes only. Type commands manually if needed.<\/span><\/i><\/p>\nStep 2: Create a Sandbox Configuration File<\/b><\/span><\/h3>\nTo customize your sandbox (e.g., to preload Office setup files), create a <\/span>.wsb<\/b> file.<\/span><\/p>\nHere’s a simple example:<\/span><\/p>\n<Configuration><\/span><\/p>\n\u00a0\u00a0<MappedFolders><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0<MappedFolder><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<HostFolder>C:\\SandboxFiles<\/HostFolder><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<ReadOnly>false<\/ReadOnly><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0<\/MappedFolder><\/span><\/p>\n\u00a0\u00a0<\/MappedFolders><\/span><\/p>\n\u00a0\u00a0<LogonCommand><\/span><\/p>\n\u00a0\u00a0\u00a0\u00a0<Command>cmd.exe<\/Command><\/span><\/p>\n\u00a0\u00a0<\/LogonCommand><\/span><\/p>\n<\/Configuration><\/span><\/p>\n <\/p>\n
Save this as <\/span>OfficeTest.wsb<\/span> on your desktop. Replace <\/span>C:\\SandboxFiles<\/span> with the folder where your Office installer and add-in files are located.<\/span><\/p>\nStep 3: Prepare Installation Files<\/b><\/span><\/h3>\nBefore launching the sandbox:<\/span><\/p>\n\n- Place your <\/span>Office 2021 Pro Plus installer<\/b> and any plugins or add-ins you want to test inside the folder specified in your .wsb file (e.g., <\/span>C:\\SandboxFiles<\/span>).<\/span> <\/li>\n
- Also include:<\/span> \n
\n- Plugin documentation<\/span> <\/li>\n
- Any required configuration files<\/span> <\/li>\n
- Dependency libraries (for COM or VSTO plugins)<\/span> <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
Step 4: Launch the Sandbox<\/b><\/span><\/h3>\n\n- Double-click the <\/span>.wsb<\/span> file you created.<\/span> <\/li>\n
- A new temporary Windows environment will boot up.<\/span> <\/li>\n
- Navigate to your mapped folder (e.g., <\/span>C:\\Users\\WDAGUtilityAccount\\Desktop\\SandboxFiles<\/span>).<\/span> <\/li>\n
- Run the Office 2021 installer.<\/span> <\/li>\n<\/ol>\n
Follow standard installation steps. Once Office is installed, you can begin plugin testing.<\/span><\/p>\nStep 5: Install and Test Your Add-ins<\/b><\/span><\/h3>\nFor Office Web Add-ins (JavaScript)<\/b><\/span><\/h4>\n\n- Open an Office app (e.g., Word).<\/span> <\/li>\n
- Go to <\/span>Insert > Get Add-ins > My Add-ins > Shared Folder<\/b>.<\/span> <\/li>\n
- Point to a manifest XML file stored in your mapped folder.<\/span> <\/li>\n<\/ol>\n
For COM or VSTO Plugins<\/b><\/span><\/h4>\n\n- Run the installer or manually register the DLL using the following command:<\/span> <\/li>\n<\/ol>\n
regsvr32 “C:\\Path\\To\\Your\\Plugin.dll”<\/span><\/p>\n\n- Launch the relevant Office application.<\/span> <\/li>\n
- The plugin should appear in the <\/span>Add-ins<\/b> tab.<\/span> <\/li>\n<\/ol>\n
Monitor how it behaves:<\/span><\/p>\n\n- Does it load correctly?<\/span> <\/li>\n
- Are there script errors?<\/span> <\/li>\n
- Is there a UI conflict?<\/span> <\/li>\n
- How does it interact with the Ribbon or task pane?<\/span> <\/li>\n<\/ul>\n
Step 6: Test for Conflicts or Performance Issues<\/b><\/span><\/h3>\nUse Office functions and features while the add-in is enabled. Pay attention to:<\/span><\/p>\n\n- Load time of Office apps<\/span> <\/li>\n
- Crashes or freezing<\/span> <\/li>\n
- Interference with other features<\/span> <\/li>\n
- Network activity if applicable (for API-driven add-ins)<\/span> <\/li>\n<\/ul>\n
You can also test scenarios like:<\/span><\/p>\n\n- File open\/save with plugin active<\/span> <\/li>\n
- Clipboard operations<\/span> <\/li>\n
- Undo\/redo with plugin commands<\/span> <\/li>\n
- Authentication flows (if the add-in connects to cloud services)<\/span> <\/li>\n<\/ul>\n
Step 7: Document Your Results<\/b><\/span><\/h3>\nBefore closing the sandbox, record:<\/span><\/p>\n\n- Success or failure to load the add-in<\/span> <\/li>\n
- Any error messages or logs<\/span> <\/li>\n
- Screenshots if UI issues are found<\/span> <\/li>\n
- Impact on Office performance<\/span> <\/li>\n<\/ul>\n
This helps with debugging or QA reporting.<\/span><\/p>\nImportant: Once the sandbox is closed, all data is wiped. Be sure to save documentation to your mapped folder if needed.<\/span><\/i><\/p>\nStep 8: Reset and Repeat<\/b><\/span><\/h3>\nOne of the biggest advantages of Sandbox is repeatability:<\/span><\/p>\n\n- Close the sandbox window<\/span> <\/li>\n
- Make changes to your add-in or environment (e.g., new plugin version)<\/span> <\/li>\n
- Re-launch the <\/span>.wsb<\/span> configuration file<\/span> <\/li>\n<\/ul>\n
You\u2019re now testing on a fresh Windows install again.<\/span><\/p>\nTroubleshooting Tips<\/b><\/span><\/h2>\n
- \n
- Open the <\/span>Start Menu<\/b>, search for <\/span>Windows Features<\/b>, and select <\/span>Turn Windows features on or off<\/b>.<\/span> <\/li>\n
- In the list, check <\/span>Windows Sandbox<\/b>.<\/span> <\/li>\n
- Click <\/span>OK<\/b>, then restart your computer when prompted.<\/span> <\/li>\n<\/ol>\n
Alternatively, you can run the following from PowerShell as Administrator:<\/span><\/p>\n
dism \/online \/Enable-Feature \/FeatureName:”Containers-DisposableClientVM” \/All<\/span><\/p>\n
Note: This is for learning purposes only. Type commands manually if needed.<\/span><\/i><\/p>\n
Step 2: Create a Sandbox Configuration File<\/b><\/span><\/h3>\n
To customize your sandbox (e.g., to preload Office setup files), create a <\/span>.wsb<\/b> file.<\/span><\/p>\n
Here’s a simple example:<\/span><\/p>\n
<Configuration><\/span><\/p>\n
\u00a0\u00a0<MappedFolders><\/span><\/p>\n
\u00a0\u00a0\u00a0\u00a0<MappedFolder><\/span><\/p>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<HostFolder>C:\\SandboxFiles<\/HostFolder><\/span><\/p>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<ReadOnly>false<\/ReadOnly><\/span><\/p>\n
\u00a0\u00a0\u00a0\u00a0<\/MappedFolder><\/span><\/p>\n
\u00a0\u00a0<\/MappedFolders><\/span><\/p>\n
\u00a0\u00a0<LogonCommand><\/span><\/p>\n
\u00a0\u00a0\u00a0\u00a0<Command>cmd.exe<\/Command><\/span><\/p>\n
\u00a0\u00a0<\/LogonCommand><\/span><\/p>\n
<\/Configuration><\/span><\/p>\n
<\/p>\n
Save this as <\/span>OfficeTest.wsb<\/span> on your desktop. Replace <\/span>C:\\SandboxFiles<\/span> with the folder where your Office installer and add-in files are located.<\/span><\/p>\n
Step 3: Prepare Installation Files<\/b><\/span><\/h3>\n
Before launching the sandbox:<\/span><\/p>\n
- \n
- Place your <\/span>Office 2021 Pro Plus installer<\/b> and any plugins or add-ins you want to test inside the folder specified in your .wsb file (e.g., <\/span>C:\\SandboxFiles<\/span>).<\/span> <\/li>\n
- Also include:<\/span> \n
- \n
- Plugin documentation<\/span> <\/li>\n
- Any required configuration files<\/span> <\/li>\n
- Dependency libraries (for COM or VSTO plugins)<\/span> <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
Step 4: Launch the Sandbox<\/b><\/span><\/h3>\n
- \n
- Double-click the <\/span>.wsb<\/span> file you created.<\/span> <\/li>\n
- A new temporary Windows environment will boot up.<\/span> <\/li>\n
- Navigate to your mapped folder (e.g., <\/span>C:\\Users\\WDAGUtilityAccount\\Desktop\\SandboxFiles<\/span>).<\/span> <\/li>\n
- Run the Office 2021 installer.<\/span> <\/li>\n<\/ol>\n
Follow standard installation steps. Once Office is installed, you can begin plugin testing.<\/span><\/p>\n
Step 5: Install and Test Your Add-ins<\/b><\/span><\/h3>\n
For Office Web Add-ins (JavaScript)<\/b><\/span><\/h4>\n
- \n
- Open an Office app (e.g., Word).<\/span> <\/li>\n
- Go to <\/span>Insert > Get Add-ins > My Add-ins > Shared Folder<\/b>.<\/span> <\/li>\n
- Point to a manifest XML file stored in your mapped folder.<\/span> <\/li>\n<\/ol>\n
For COM or VSTO Plugins<\/b><\/span><\/h4>\n
- \n
- Run the installer or manually register the DLL using the following command:<\/span> <\/li>\n<\/ol>\n
regsvr32 “C:\\Path\\To\\Your\\Plugin.dll”<\/span><\/p>\n
- \n
- Launch the relevant Office application.<\/span> <\/li>\n
- The plugin should appear in the <\/span>Add-ins<\/b> tab.<\/span> <\/li>\n<\/ol>\n
Monitor how it behaves:<\/span><\/p>\n
- \n
- Does it load correctly?<\/span> <\/li>\n
- Are there script errors?<\/span> <\/li>\n
- Is there a UI conflict?<\/span> <\/li>\n
- How does it interact with the Ribbon or task pane?<\/span> <\/li>\n<\/ul>\n
Step 6: Test for Conflicts or Performance Issues<\/b><\/span><\/h3>\n
Use Office functions and features while the add-in is enabled. Pay attention to:<\/span><\/p>\n
- \n
- Load time of Office apps<\/span> <\/li>\n
- Crashes or freezing<\/span> <\/li>\n
- Interference with other features<\/span> <\/li>\n
- Network activity if applicable (for API-driven add-ins)<\/span> <\/li>\n<\/ul>\n
You can also test scenarios like:<\/span><\/p>\n
- \n
- File open\/save with plugin active<\/span> <\/li>\n
- Clipboard operations<\/span> <\/li>\n
- Undo\/redo with plugin commands<\/span> <\/li>\n
- Authentication flows (if the add-in connects to cloud services)<\/span> <\/li>\n<\/ul>\n
Step 7: Document Your Results<\/b><\/span><\/h3>\n
Before closing the sandbox, record:<\/span><\/p>\n
- \n
- Success or failure to load the add-in<\/span> <\/li>\n
- Any error messages or logs<\/span> <\/li>\n
- Screenshots if UI issues are found<\/span> <\/li>\n
- Impact on Office performance<\/span> <\/li>\n<\/ul>\n
This helps with debugging or QA reporting.<\/span><\/p>\n
Important: Once the sandbox is closed, all data is wiped. Be sure to save documentation to your mapped folder if needed.<\/span><\/i><\/p>\n
Step 8: Reset and Repeat<\/b><\/span><\/h3>\n
One of the biggest advantages of Sandbox is repeatability:<\/span><\/p>\n
- \n
- Close the sandbox window<\/span> <\/li>\n
- Make changes to your add-in or environment (e.g., new plugin version)<\/span> <\/li>\n
- Re-launch the <\/span>.wsb<\/span> configuration file<\/span> <\/li>\n<\/ul>\n
You\u2019re now testing on a fresh Windows install again.<\/span><\/p>\n
Troubleshooting Tips<\/b><\/span><\/h2>\n
- Make changes to your add-in or environment (e.g., new plugin version)<\/span> <\/li>\n
- Any error messages or logs<\/span> <\/li>\n
- Clipboard operations<\/span> <\/li>\n
- Crashes or freezing<\/span> <\/li>\n
- Are there script errors?<\/span> <\/li>\n
- The plugin should appear in the <\/span>Add-ins<\/b> tab.<\/span> <\/li>\n<\/ol>\n
- Launch the relevant Office application.<\/span> <\/li>\n
- Go to <\/span>Insert > Get Add-ins > My Add-ins > Shared Folder<\/b>.<\/span> <\/li>\n
- A new temporary Windows environment will boot up.<\/span> <\/li>\n
- Any required configuration files<\/span> <\/li>\n
- Also include:<\/span> \n
- In the list, check <\/span>Windows Sandbox<\/b>.<\/span> <\/li>\n