[Community tool] Find the GPO, registry value and Intune setting for any Office ribbon button
Hi everyone, as a technical service owner for Microsoft 365 Apps, one question comes up for me again and again: which policy actually controls this button or option? The information is all there – in the Office ADMX/ADML templates, the Office Fluent UI control ID lists, the Intune Settings Catalog and many Learn articles. But I never found it in one place, so every answer meant connecting several sources by hand. Especially when onboarding new colleagues, this costs a lot of time. So I built a free community tool for it: Office Admin Explorer https://tools.pascal-donath.de/office-admin-explorer/ How it works It's a clickable mock of Word, Excel, PowerPoint and Outlook (ribbon, File menu, Options, Trust Center). Click any element and you get: idMso and Policy ID (for customUI and the "Disable commands" policy) the ADMX policy with its exact path in Group Policy Management the registry value it writes, with ready-to-copy PowerShell or .reg the matching Intune Settings Catalog entry Cloud Policy notes, step-by-step guides and Microsoft Learn links The search covers all Office ADMX policies (2,400+) and command IDs (8,000+), including elements that aren't part of the mock. Also included Ribbon builder – hide or disable buttons, groups or tabs and export the result as customUI XML, a macro-free add-in (.dotx / .xlam / .ppam) or the "Disable commands" policy for Group Policy and Intune Deployment view – configuration.xml generator for the Office Deployment Tool User Support view – typical user problems: symptom → cause → fix Policy names and registry values are checked against Microsoft's ADMX/ADML files, and the Intune mapping against the Graph settings catalog. It runs in the browser without sign-in and is available in English and German. Please test any configuration on a lab device or pilot group first. I'd like your input How do you handle this today – ADMX search, Group Policy Search, the Intune catalog, your own documentation? Which Office settings do you get asked about most often? I'd like to add the most requested ones next. If you find a wrong or outdated entry, every entry has a "Report it on GitHub" link – corrections are very welcome. Thanks! Pascal --- *Transparency note: The tool was developed with the help of AI. The content is based on my own admin experience, and policy names, registry values and Intune mappings are validated automatically against Microsoft's official sources (ADMX/ADML templates, Fluent UI control lists, Microsoft Graph settings catalog). This is a community project and not affiliated with Microsoft.*
Bookings Page - Some Error Occurred
Having an issue with a Microsoft Booking page where it keeps encountering the "Some error occurred." when loading. This Bookings page was confirmed working from creation date of May 14th, 2026 to recently, September 14th, 2026. As far as the user has told me, they had changed nothing between those dates. I had worked with the user and tried the following troubleshooting steps: 1.) I had the user switch the publishing from "Available to anyone" to "No self-service". Confirmed that the page then started showing a "Bad request" error and then changed the setting back to "Available to anyone." This did not fix the issue and the "Some error occurred" was still happening. 2.) Confirmed with the user if there was anything that changed that might be causing syncing issues between the staff calendars and the Bookings page. Found two instances (1 user who had they name changed and 1 user who went on leave of absence) and decided to see if these might be causing issues. The user who was on LOA was removed and this did not fix the issue. The user who had their name changed recently was appearing with the correct names in other Bookings pages but still had their old name in this one. Once removed and readded to this Bookings page their name was updated to be correct, but this did not solve the issue. 3.) I had the user check to see if the automated emails from the Bookings were still sending and they were confirmed to be sending. These automated emails do have specific Service links in them that are being received by customers and are working at this time. In regards to the above point, while I was working with the user who created the Bookings page, we found that the Calendar in the Bookings page was not working correctly. It does not show the Bookings that were created consistently and would usually appear blank. The Services that were created have all disappeared, but it looks like a filter is being forced. It shows "Services 52 of 0" and the user tried to remove the filter and nothing occurs. What are some next steps in troubleshooting the Bookings page?
Office Home & Business 2019 license no longer recognized after reinstall ("No license found")
Hello everyone, I'm looking for some help because Microsoft Support has not been able to solve this issue. I own a genuine perpetual license of Office Home & Business 2019 for Mac, linked to my Microsoft account since August 2019. The license is still listed under Services & Subscriptions, but Office no longer activates. My hardware MacBook Pro (Retina, 13-inch, Late 2012) Model: MacBookPro10,2 Intel Core i5 8 GB RAM macOS Ventura 13.7.8 Installed using OpenCore Legacy Patcher Office version originally working: 16.78 Later tested with 16.101 and 16.93 Same result on every version What happened Office had already been successfully activated and worked normally. I was able to: create documents edit documents save documents After restarting the Mac, Office suddenly requested activation again. Since then it has never activated successfully. Initially Office failed to activate with an unknown error. After completely uninstalling and reinstalling Office using Microsoft's installer, the activation process changed. I can now successfully sign in with my Microsoft account, but after authentication Office displays: "No license found for this account." My Office Home & Business 2019 license is still present in my Microsoft account under Services & Subscriptions. Even though my Microsoft account clearly owns Office Home & Business 2019 for Mac. Microsoft account The license appears correctly under: Services & Subscriptions Office Home & Business 2019 for Mac Added to my account on August 7, 2019. The website instructs me to open an Office application and sign in to activate. Everything I've already tried Uninstalled Office completely Installed Office again using Microsoft's installer Installed Office 16.78 Installed Office 16.93 Updated to Office 16.101 Removed Office containers Removed Group Containers Deleted OneAuth cache Deleted Entrabroker cache Removed activation tokens Cleared Office preferences Signed out and signed back into Microsoft account Deleted Office credentials from Keychain Reinstalled Microsoft AutoUpdate Verified no MDM profile exists Verified Internet Accounts Verified Microsoft account Microsoft Support remotely accessed my Mac and repeated all troubleshooting steps Nothing solved the issue. Additional information Running: defaults read com.microsoft.office returns: OfficeActivationLicense = NoLicense although: OfficeActivationEmailAddress = email address removed for privacy reasons is correctly detected. The activation window successfully reaches Microsoft's login page. Office now asks for my Microsoft account credentials. Authentication completes successfully. After a few seconds Office reports: "No license found for this account." It then offers only two options: Buy Microsoft 365 Use another account Microsoft Support remotely connected to my Mac, completely removed Office, installed a newer official installer, and the problem remained exactly the same. My question Has anyone experienced this after reinstalling Office 2019? Could this be: a licensing server issue? an incompatibility introduced after Office 2019 reached end of support? an activation problem related to OpenCore Legacy Patcher? something else? I would really appreciate any suggestions. Thank you very much. Additional notes: The Office license has been associated with the same Microsoft account since 2019. The same installation was successfully activated and worked normally before the problem started. The issue only appeared after restarting the Mac. Microsoft Support has already remotely accessed my computer and could not resolve the problem.
New Entra ID group device criteria scoping is missing from Cloud Update
Hi, the New Entra ID group device criteria scoping is missing from Cloud Update. Message center says that it should be GA late July, but here we are and it's still not there. Is there a way to know when should we expect it to rollout for real? Thks in advance and don't hesitate if you have any questions
How can specific users be exempted from a tenant-scoped Microsoft 365 Apps Policy?
Hello, I am looking for guidance regarding Microsoft 365 Apps Cloud Policy Service behavior and policy precedence. Current configuration: In Microsoft 365 Apps Admin Center → Policy Management (config.office.com), we have the following policies: Policy 1 Name: Shorten Meeting Global Scope: Tenant Priority: 0 Configured settings: Shorten appointments and meetings = Enabled Reduce the end time of short appointments and meetings = 5 minutes Reduce the end time of long appointments and meetings = 10 minutes Policy 2 Name: Test Scope: User (Security Group) Priority: 1 Assigned only to a dedicated test group Relevant settings configured as Not Configured Observed client behavior: On corporate-managed devices, affected users receive the following registry values: HKCU\Software\Policies\Microsoft\Cloud\Office\16.0\Outlook\Options\Calendar shortenevents = End_Early endearlyshort = 5 endearlylong = 10 The Outlook option: File > Options > Calendar > Shorten appointments and meetings is greyed out. Additional validation: Using the same Microsoft 365 account on an external non-corporate device: The above registry path is not present. The Outlook option is editable. Testing performed: A user-scoped Cloud Policy was created and assigned to a dedicated security group. For the "Shorten appointments and meetings" setting, only the following options are available: Enabled Not Configured There is no Disabled option. but the Tenant policy continued to apply and the Outlook option remained locked. Questions Is there a supported way to exempt specific users from a tenant-scoped Microsoft 365 Apps Cloud Policy when the setting only supports "Enabled" and "Not Configured" and does not provide a "Disabled" option? Does Not Configured in a User-scoped policy allow evaluation to continue to the lower-priority Tenant policy? If policy precedence is changed so that: Test Policy = Priority 0 Tenant Policy = Priority 1 would the User policy potentially suppress the Tenant setting? Is there a supported way in Microsoft 365 Apps Cloud Policy Service to provide exceptions for specific users while keeping the Tenant policy as the organizational default? Has anyone successfully implemented an exclusion or override scenario for the "Shorten appointments and meetings" setting? Any guidance or documentation references would be greatly appreciated. Thank you.
Microsoft 365 Apps SHOULD NOT overwrite Office 2019/2021 one-time retail installs
I want to raise a serious concern about Microsoft 365 Apps being imposed over existing Office 2019/2021 installations that were activated with legitimate one-time installation retail keys. In our case, these are not Microsoft 365 subscriptions and they are not licenses we can simply deactivate and reactivate freely. They are one-time installation retail keys. Once the product has been installed and activated, removing Office and reinstalling it later can make the original key unusable or trigger “already used” activation problems. That is precisely why the current behavior is so damaging. We have PCs with legitimate Office 2019/2021 installations. These machines did not request a migration to Microsoft 365 Apps. However, after internet connection, Office update activity, or Microsoft account interaction, Office appears to silently update, convert, or replace the existing retail installation with the Microsoft 365 Apps version. This is not a minor inconvenience. It creates a serious licensing and operational problem: -A valid one-time Office 2019/2021 installation is replaced by Microsoft 365 Apps without clear, explicit consent. -The original retail installation is no longer cleanly usable. -Fixing the issue requires uninstalling Office, removing Click-to-Run/licensing/account leftovers, and reinstalling the previous Office 2019/2021 version. -But because these keys are one-time installation keys, that reinstall process can render the original key unusable or create activation failures. -In practice, a forced Microsoft 365 conversion can destroy the value of a legitimate one-time Office license. From a user’s perspective, this looks less like a normal software update and more like an exploitative commercial strategy: using Microsoft’s control over Office updates, account sign-ins, Click-to-Run, and activation systems to push already-paid retail users toward Microsoft 365 subscriptions. Even if Microsoft does not intend that result, the practical effect is that users who already paid for Office 2019/2021 can lose practical access to their licensed product and are then nudged toward paying again through a subscription. This should not happen. A perpetual or one-time installation Office license and Microsoft 365 Apps are different products with different licensing models. Microsoft should not silently replace or convert one into the other because a Microsoft 365 account exists on the PC, because the user signs into Office, because OneDrive is present, or because Office updates are enabled. At minimum, Microsoft should provide: -A clear opt-in confirmation before replacing, converting, upgrading, or rebranding Office 2019/2021 retail installations as Microsoft 365 Apps. -A supported way to block Microsoft 365 Apps from taking over one-time installation Office versions. -A clean removal tool that fully removes Microsoft 365 Apps, Click-to-Run leftovers, licensing remnants, and account-based activation conflicts. -A reliable way to restore the original Office 2019/2021 retail installation without invalidating or losing the original one-time key. -Clear separation between Windows account sign-in, OneDrive sign-in, Microsoft 365 entitlement, and local Office retail activation. Users who purchased legitimate one-time installation Office licenses should not be forced into Microsoft 365 Apps by unclear update behavior. If Microsoft wants users to move to Microsoft 365, that should be a deliberate, informed choice — not a silent process that leaves the user cleaning up the installation and losing access to a paid retail license. I am not asking how to install Microsoft 365. I am asking Microsoft to stop Microsoft 365 Apps from taking over valid one-time Office 2019/2021 installations without explicit consent.
Searching in a Microsoft List
How could a user restrict their search to a particular value in a particular field? Let's say I need to search for the value 'Williams' in the 'Company' field. I could enter "Williams" into the search bar, but the hits would include all items that contain the word "Williams" in any field. I want to restrict the search. How can one do that?Store-published Word add-in can't read or write the open document
We published a Word add-in to the Microsoft Store and ran into something odd that I'm hoping someone here has seen before. The add-in installs and opens fine. Signing in, the chat assistant, browsing our documents, moving between tabs ; all of that works. The problem is anything that has to actually read or change the open Word document. Pulling a doc in from our Sync tab, dropping in a template, running a compliance check on the current document ; none of it does anything. No error, no message, it just doesn't happen. So basically if a feature only shows stuff or talks to our own server it's fine, but the second it needs the actual document, nothing. A few things I'm trying to figure out: - Is this a known thing with Store-installed add-ins vs when you're just testing it? - Any good way to see why those actions are failing when nothing shows up on screen? Happy to share more detail. Thanks in advance.
Issue with viewing mode for E5 licensed users
I'm a sysadmin for a Health care provider in Sweden and we have an issue with users with an E5 license loading into Office apps in view-mode. As far as I know we are a coupe of organisations providing health care that have this same issue. Background: We have a mix of F3 and E5 licenses and sometimes the F3 licensed users need to view documents that contains info that isn't allowed to be saved in the cloud. To minimize the popups that show up when a user starts word unlicensed we have a GPO (viewer mode) that says that it should open i view-mode. Per my understanding this GPO is device based and not user based. However, this also affects the users of E5 license who regularly change workstations, easily 5-10 devices in a day. Since they should be able to view and edit documents in office apps it causes frustration and confusion when they load into view-mode and have to log out and then in again (or update license) and restart the program. Our computers devices are Microsoft Entra hybrid joined and shared computer licensing is enabled. Are there any solutions or viable workarounds for this issue? It's not complicated for users to handle but frustrating and causes a lot of tickets to the support team. Unsure if I'll be able to participate due to the time zone difference but will appreciate any and all help. /Per Ekholm[Update on Microsoft 365 Copilot Mac app issue]
We have identified the root cause of the issue currently affecting some users on Microsoft 365 Copilot Mac app, starting with version 1.2601 released on January 27. A fix has been prepared for the same and will be delivered via Microsoft AutoUpdate (MAU) within the next 48 hours. Please note that the app may not function as expected if MAU configurations are being managed through MDM. To mitigate, tenant administrators can remove the LCID key from their MAU configuration, as illustrated below. Kindly let us know if the issue persists for you beyond this timeline.
