Turning off email notifications about new comments in one certain file
Hi All! I found a solution to turn off all email notifications on new comments in my shared files (through settings on SharePoint), but it doesn't really solve my problem. In project files I work on with my colleagues, email notifications are helpful for monitoring workflows and streamline the process. At the same time, I'm an owner of yearly excel files shared with a big team in order to monitor the work on all clients and automate the visualization of it, but it gets commented on a lot and I don't need to get all of that on my Outlook. Is there any way to turn off email notifications about new comments for just one file without turning them off on all my shared files? Kind regards, Jakub Banasik
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.
PLEASE HELP ME. Can't Get Formulas In Word To Work?
I know how to use formulas in EXCEL and I know WORD isn't EXCEL. But I'm trying to enter a very simple formula into a table in a WORD document to calculate simple macro-nutrients. The formula is very simple. Each gram of carbs is 4 calories. I'm just trying to enter a formula that automatically multiples the number of carbs by 4 so I don't have to manually do the math on my own every time. As you can see in my screenshot, I got it to work by entering (=B2*4). The problem is the formula doesn't stay there. It instantly vanishes once entered. So if I change the number of carbs from 100 which is 400 calories, to 200 which is 800 calories, the formula doesn't automatically update the total calories because the formula disappeared once entered. I just want to know if I can enter the formula in a way which causes it to permanently stay in the cell so it always updates the total calories whenever I change the number of carbs? Just like EXCEL always does? And how to do that? If it's not possible, that's okay. I will simply consider going back to EXCEL then.Word Copilot attachments fail with NoTokenObtained
Word Copilot cannot read local or cloud attachments with my Microsoft account. Cloud file attachment opens OneDrive Picker but fails with NoTokenObtained, timeout, or “Sorry, something went wrong.” Local files are accepted but reported as empty/corrupted. The same files work correctly in Microsoft 365 Copilot Chat with the same account. The issue reproduces on different computers, different networks, new Edge profile, new Windows user, and Word for the web without Office desktop installed. Word Copilot can read the active document, so only the attachment pipeline appears broken. Correlation IDs: 49a92ea2-7068-2001-bf16-3cf7d0c388fd and b39b30a2-b012-f000-cf51-72bd844c5dea. Please escalate to Word Copilot / OneDrive File Picker / Microsoft 365 Copilot engineering.
Free 200-page Advanced Microsoft Word Tutorial for Theses, Reports and Publications
I am a professor at Ghent University in Belgium and I have written a free tutorial (200+ pages) on advanced Microsoft Word. The tutorial is useful for everybody who is writing larger documents, such as technical reports, MSc or PhD theses, publications, law documents, etc. Topics include: Paragraph styles Field codes (SEQ, STYLEREF, REF) Bookmarks and cross-references Equation numbering Multi-level lists Headers and footers Sections VBA macros Reference management Word XML structure PDF/A export The document is freely available and feedback is welcome. Here is the download link: https://composites.ugent.be/downloads.html Best regards, Wim VAN PAEPEGEM
Cursor flickers excessively when STYLEREF field is used in header with multiple pages
[Performance & Graphic Issue] Word cursor flickers excessively when STYLEREF field is used in header with multiple pages Edit: This issue wont appear at the first time. You can try to edit for a bit time or just scroll a little bit and you will see flickers excessively in a unpleasant speed that ruins your whole writting experience... Description I have encountered a reproducible performance issue in Microsoft Word that causes the text cursor (insertion point) to flicker excessively and continuously when a STYLEREF field is present in the document header. Steps to Reproduce Open Microsoft Word and create a new blank document. Apply the "Heading 1" style to a few paragraphs in the body (e.g., "Chapter 1", "Chapter 2", ...). Double-click the header area to enter the header editing mode. Insert a STYLEREF field that references "Heading 1": Insert > Quick Parts > Field > StyleRef > Heading 1. Close the header and add enough content to the body so the document spans approximately 5–6 pages (e.g., by pressing Enter repeatedly or generating dummy text). Observe the text cursor behavior while typing or simply moving the cursor in the body. Actual Result The text cursor begins to flicker rapidly and continuously once the document reaches about 5–6 pages. The flickering stops immediately when the header/footer area is hidden. I Think the issue is directly correlated with the presence of the STYLEREF field in the header. Expected Result The cursor should remain stable and not flicker, regardless of the presence of the STYLEREF field or the document length. Environment Application: Microsoft Word for Microsoft 365 Version: 2607 (Current Channel) OS: Windows 10 22H2 (Build 19045) Additional Info: This issue occurs in a brand-new blank document with no third-party add-ins or custom templates. The problem is 100% reproducible. Severity This significantly impacts usability, especially when editing longer documents such as theses, reports, or books where chapter titles are commonly displayed in headers. The constant cursor flickering is visually distracting and causes eye strain during extended editing sessions. Note The above report was drafted and translated into English with the assistance of Deepseek, but all the information provided is based on my own manual testing and observations. The issue was discovered during my actual document editing workflow, and I have confirmed through repeated testing that it is directly related to the STYLEREF field.
