Latest update of Word has changed my doc format. print layout not working
Latest update of Word has changed my doc format. first, print layout not working, i copied the text to new doc. session break-continous and justified paragraphs. inserting session breaks aligns the last line to left. using Shift+Enter justifies the paragraph but also adds a blank line after the paragraph. FYI i have composed a book in hindi language on with formatting and hyperlink. please support. screenshot of pdf shared
[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.*
OneDrive files opened from Finder not recognized as cloud files on Mac
Office for Mac: OneDrive files opened from Finder no longer recognized as cloud files – AutoSave disabled Hi everyone, I am experiencing a persistent issue with Microsoft 365 for Mac and OneDrive that started suddenly around August 10, 2026. The same setup and workflow had worked without problems for more than two years before that. Problem My Office files are stored in OneDrive and synchronized to my Mac via the standard macOS File Provider. When I open an Excel or Word file by double-clicking it in Finder, the Office application opens the file, but it apparently does not recognize it correctly as a OneDrive/cloud file. For example: AutoSave is disabled real-time co-authoring does not work as expected when I try to enable AutoSave manually, Office behaves as if the file were local and asks me to upload/save it to OneDrive – even though the file is already stored and synchronized in OneDrive However, if I open the exact same file from within Excel or Word via the OneDrive/Online Locations option, everything works correctly: AutoSave is enabled immediately co-authoring works changes made by another user appear in real time This behavior is reproducible with multiple files and affects both Excel and Word, so it does not appear to be an issue with one particular workbook or application. Environment MacBook Air M2 current macOS version current Microsoft 365 version current OneDrive version OneDrive Personal files synchronized through the standard macOS File Provider I have also tested opening files directly from: ~/Library/CloudStorage/OneDrive/... The result is the same: when opened from Finder, Office does not appear to recognize the file correctly as a cloud file and AutoSave remains disabled. Troubleshooting already performed I have already: completely reset and reconfigured OneDrive allowed OneDrive to fully resynchronize verified the files and folders in OneDrive on the web confirmed that OneDrive reports everything as synchronized restarted Finder and macOS removed and recreated Finder shortcuts/favorites tested without Finder favorites or aliases tested directly from ~/Library/CloudStorage/OneDrive updated macOS updated all Microsoft 365 applications updated OneDrive None of these steps changed the behavior. Key diagnostic result The following comparison is consistently reproducible: Finder → OneDrive file → double-click → Excel/Word → AutoSave OFF → file appears not to be recognized as an active OneDrive cloud document → co-authoring does not work correctly Excel/Word → Open → OneDrive/Online Locations → same file → AutoSave ON immediately → cloud functionality works → co-authoring works correctly This suggests that OneDrive synchronization itself is functioning correctly. The issue seems specifically related to the handoff between macOS Finder / Apple File Provider / OneDrive and Microsoft 365 for Mac when a OneDrive file is opened from Finder. Important detail This is not a workflow that has never worked on macOS. For more than two years, we routinely opened our synchronized OneDrive Word and Excel files directly from Finder. Office recognized them as cloud files, AutoSave was available, and collaborative editing worked normally. The behavior changed suddenly around August 10, 2026, without us intentionally changing the OneDrive folder structure or our workflow. Question Has anyone else encountered this recently? In particular: Is this a known regression in Microsoft 365 for Mac, OneDrive for Mac, or their integration with Apple's File Provider? Why would Office recognize a file as a OneDrive cloud document when opened through the application's Online Locations, but not when the exact same synchronized file is opened from Finder? Is there a way to reset or repair the Microsoft 365/OneDrive cloud-file recognition or File Provider integration without resetting the entire OneDrive again? Are there any relevant logs, caches or diagnostics that could show why Office considers a Finder-opened OneDrive file to be local? Opening every document through the Office application's Online Locations is a possible workaround, but it is not a practical long-term solution when working with a larger shared folder structure in Finder. I have already contacted both Apple Support and Microsoft Support. Apple referred me to Microsoft, and Microsoft Support subsequently recommended that I raise the issue here in the Tech Community. Any insight from Microsoft staff, MVPs or others familiar with Microsoft 365 for Mac, OneDrive and the macOS File Provider would be greatly appreciated.
Word corruption
I am using Microsoft 365 on Mac running Tahoe 26.3.1. I downloaded a Google document from a client as a .docx Word document. This is something I do often. My client is also using a Mac. The Word document has corruptions in it, full lines of text are appearing as lines (like a barcode) and there seem to be letters and symbols stacked up on top of each other. Screenshots attached. I have tried saving as a .doc Word document but the corruptions are still there. If I select all of the text and change the font, the corruptions are still there. I copied the text into Text Edit and converted to plain text. The corruptions disappear in Text Edit but so does any text that was there, sentences are incomplete. If I copy and paste this plain text into a new Word document, the corruptions reappear. If I import the Plain Text into InDesign, the corruptions reappear. If I copy and paste the plain text into InDesign, the corruptions reappear. This strikes me as very odd because as far as I know Plain Text should remove any corruptions. My client says that they see no corruptions in the Word doc or in the Plain Text doc that they created. But when they send these docs in email, the corruptions are still there. I spent 4 hours with Microsoft Support yesterday trying to figure out the problem and when they couldn't figure it out, they just closed and left the chat.... I would love to let my client know what they can do to fix this on their end so that we can move forward with the project. Any suggestions are appreciated!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.Word - Insert Key
Why doesn't the Insert key on the keyboard do anything? It's a key on the keyboard, make use of it! Most obviously, why doesn't pressing it make it change to overtype text. Why when in tables doesn't the insert key allow you to add rows to a table where you currently are? Today I found it very painful to add more than one row to a table. Even after an internet search I didn't find an easy way quickly. Surly making use of the insert key and pressing it once per new row would be the most easy? It works like this in MS Project.Finding the recycling bin on Microsoft word
I have had to go on a wild goose chase, to be quite frank with you, for the recycling bin on word. I was about to lock in and have my “academic comeback”, as the bairns say on social media platforms such as TikTok and Instagram, and I was taken off my track to find this stupid recycling bin. I am still yet to find and it and I am very unhappy, not only was google no help but so was Microsoft. 1/ Micro out of 10. Very upset need I remind you. Those special documents are now swimming in the land of the meta, in the river of the Zuckerberg and I can’t do anything about it. Get with the programme Microsoft. sincerely, disappointed.
