'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Azure Information Protection Add-In Keeps Disabling in Excel
Question details
The user needs to prevent the Azure Information Protection (AIP) add-in from automatically disabling in Excel.
- Product
- Microsoft Excel
- Device & OS
- not provided
- Scenario
- Attempting to use the legacy Azure Information Protection add-in for sensitivity labeling in newer Microsoft 365 builds.
- Observed behavior
- The Azure Information Protection add-in is disabled by default and continues to disable itself automatically upon opening Excel.
Ensure you have administrative privileges on your computer to modify Group Policy settings, and verify your current Microsoft 365 version.
Enable the Legacy AIP Add-in via Group Policy
Modify the Group Policy settings to force the legacy Azure Information Protection add-in to stay enabled in Microsoft 365 Apps.
Starting with Microsoft Office version 2302, the legacy Azure Information Protection (AIP) add-in is disabled by default. This is because sensitivity labeling is now handled natively through newer built-in Office capabilities. If your organization still requires the legacy add-in, you must explicitly enable it through a Group Policy configuration.
Press the Windows key + R to open the Run dialog, type 'gpedit.msc', and press Enter.
In the left pane, navigate to User Configuration > Administrative Templates > Microsoft Office 2016 > Security Settings.
Locate and double-click the policy named 'Use the Azure Information Protection add-in for sensitivity labeling'.
Select 'Enabled' and set the policy value to 1. Click 'Apply' and then 'OK' to save your changes.
Close any open instances of Microsoft Excel and restart the application for the new policy to take effect.
Looking for a Stable, Lightweight Office Suite? Try WPS Office
If frequent Microsoft 365 updates are altering your workflows and disabling preferred add-ins, consider switching to WPS Office. It provides a lightweight, stable, and highly compatible alternative for handling your spreadsheets without requiring complex Group Policy configurations.
- 1. Download WPS Office: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the Software: Run the downloaded installer and follow the on-screen instructions to complete the setup.
- 3. Open Your Spreadsheets: Launch WPS Spreadsheet and instantly open your existing Excel files with full compatibility.
Frequently Asked Questions
Why is the Azure Information Protection add-in suddenly disabled?
Starting with Microsoft 365 Apps version 2302, Microsoft disables the legacy AIP add-in by default because sensitivity labeling features are now built directly into Office applications via Microsoft Purview.
Can I use sensitivity labels without the legacy AIP add-in?
Yes. Newer versions of Microsoft 365 Apps have native built-in sensitivity labeling capabilities that replace the need for the legacy Azure Information Protection add-in.
How do I access Group Policy Editor if I am on Windows Home?
The Local Group Policy Editor (gpedit.msc) is not officially included in Windows Home editions. You may need to upgrade to Windows Pro or Enterprise, or apply the policy via Registry Editor if supported by your IT administrator.
