Feature Request: Language-Based Font Categorization (Word, PowerPoint, & Microsoft 365 Apps)
Dear Microsoft Office Team, I am a regular user of Microsoft 365 applications, and I truly appreciate the continuous improvements made to the software. I would like to suggest a feature enhancement that would significantly improve the workflow for users working with multi-language documents and presentations across all design-dependent Microsoft apps (such as Word and PowerPoint): Categorized and language-separated font drop-down menus. Currently, when dealing with a large library of installed fonts, the font list mixes all languages together (Latin, Arabic, and other scripts). This makes it extremely difficult to compare font styles quickly, As a graphic designer, this issue is incredibly frustrating; when comparing fonts in programs like Word or PowerPoint, users are forced to constantly scroll up and down, often losing track of the font they liked. Personally, this leads me to either write down the names of the fonts on a separate sheet of paper or repeatedly type out the same sentence—applying a different font to each version—just so I can compare them side by side. My suggestion is to: Provide a clean, structured view where users can easily browse and compare font styles within the same language family without scrolling through long mixed list. Group fonts by language/script categories (e.g., all Arabic fonts grouped together, all English/Latin fonts grouped together, and so on). Extend this feature across all Office apps that rely heavily on typography and design (Word, PowerPoint, etc.). This feature would save an immense amount of time, reduce friction in document/presentation design, and elevate the overall user experience—much like how professional design software handles typography. Thank you for your time, consideration, and dedication to making Microsoft 365 better for everyone. Best regards, MINA-eNjOy
[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.*
Allow administrators to configure default field selection for Word Templates
Description When creating a new Word Template in Business Central, the default field selection is currently based on field type. Text fields and primary key fields are included by default, while many other useful fields are excluded. This creates extra work for users because important business fields such as: Post Code Country/Region Code Currency Code Payment Terms Code Shipment Method Code Salesperson Code must be manually selected every time a new Word Template is created. The challenge is that even if a Word document already contains merge fields for these values, the fields are unavailable unless they are explicitly selected in the template setup. As a result, organizations must repeatedly perform the same field selection for every new template. Suggested improvement Provide a page where administrators can configure default Word Template fields per table. Example: Table Default included fields Customer Post Code, Country/Region Code, E-Mail Contact Post Code, Mobile Phone No., Country/Region Code Vendor Post Code, Payment Terms Code This would: Reduce repetitive configuration work. Ensure consistency across templates. Improve usability for non-technical users. Reduce support questions about missing merge fields. The current behaviour could remain the default, while organizations could optionally define their own standard field selection. Business impact Organizations that use Word Templates extensively often create many templates over time. Repeatedly selecting the same fields for every template is time-consuming and error-prone. Central administration of default field selections would improve productivity and template consistency.
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?
Is there a way to create role-specific competency frameworks in Microsoft 365?
We already have a lot of employee information in Entra ID, like job title, department, manager, location, and other user attributes. What I’m trying to figure out is whether we can use those attributes to automatically assign different competency frameworks to different groups of employees. For example, engineers would have one set of competencies, sales another, and managers would have additional leadership competencies. Ideally this would update automatically when someone changes role or department in Entra rather than HR maintaining everything manually. Has anyone built something like this with Entra + SharePoint/Power Automate, or is there a better way to manage competency frameworks while still keeping Microsoft 365 as the source of employee data?
How much of your Microsoft 365 environment can you actually see at once?
Not how many users you have. Not how many sites, teams, apps or flows you have. How much of it can you actually see connected together? I've been working across Microsoft 365 environments for a while, and I kept running into the same thing. There is no shortage of information. If anything, there is probably too much of it. Users, groups, permissions, SharePoint, Teams, Power Apps, Power Automate, Power BI, Dataverse, OneDrive, Exchange, Intune, licensing, configuration... It's all there. But when you're actually trying to understand how everything fits together, it can be a different story. You open one blade. Find something. Open another. Cross-check it. Go back. Open something else. Before long, you're jumping between different parts of the tenant trying to build the bigger picture in your head. And if you're working with larger environments, that gets difficult pretty quickly. The information isn't necessarily missing. The relationships between the information are what can be difficult to see. That got me thinking about a slightly different question: Instead of "where do I find this information?" "Show me what's connected to this." That's where VisibleState started. Start anywhere. Follow the connections. Imagine starting with a single user. Instead of seeing that user simply as a record with a list of properties, imagine being able to explore the relationships around them: User → Groups → SharePoint → Teams → Power Apps → Power Automate → Power BI → Dataverse → OneDrive → Exchange → Intune Then the questions become different: What does this user have access to? Is that access direct or coming through a group? What resources are connected to them? What depends on something they're associated with? Which licenses are involved? Are there relationships that look unusual? If something changes, what else might be affected? Those questions aren't necessarily about finding another piece of information. They're about putting information that already exists into context. A report can tell you that something exists. A connected view helps you understand what it is connected to. Illustrative example below — not a real customer environment. I'm not suggesting Microsoft 365 doesn't already give us this information Quite the opposite. Microsoft 365 already gives administrators an incredible amount of information and tooling. The thing I've been thinking about is what happens when you want to look across those boundaries. Sometimes I don't want another export. I don't want another list. I don't necessarily want another dashboard. I want to start with something I'm looking at and ask: "What's connected to this?" And then keep following the trail. That's the idea I'm exploring with VisibleState. The interesting part is what happens when you change the viewpoint The same relationships can be useful for completely different reasons. For example: Administrators may want to understand access, permissions and dependencies. Security and governance teams may want to find unusual relationships or exceptions. Compliance teams may need to understand who can access something and why. People managing multiple environments may want a consistent way to understand what's there without rebuilding the picture manually every time. Leadership may not need to see the graph at all. They may simply want to know what's important, what's exposed and what could be affected. It's still the same underlying environment. You're just looking at it from a different angle. And that's where I think things get interesting. Where I'm at with it VisibleState started as something I was building to make my own work easier. I was spending a lot of time investigating environments, tracing access and putting information together for reports. The individual tasks weren't necessarily difficult. It was the jumping between different places and reconstructing the bigger picture that took the time. So I started building something that would let me approach the environment through the relationships instead. It's grown quite a bit from where it started, and I'm continuing to build it. I'm not posting this as a product launch, and I'm not looking for people to sign up. I'm genuinely interested in whether the problem I'm seeing is familiar to other people working with Microsoft 365. So I'm curious... If you could start with any object in your Microsoft 365 environment and immediately see what it's connected to, where would you start? Would it be: Users and access Groups and permissions SharePoint and Teams Power Apps, Power Automate, Power BI and Dataverse Licensing and resources Governance and unusual relationships Something completely different Maybe you've already got a good way of doing this. Maybe you still find yourself jumping between different services and piecing things together manually. Or maybe I'm looking at the problem from the wrong direction. What's the one relationship in your Microsoft 365 environment that you wish you could see instantly?
