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-eNjOyAutoSave disabled when opening SharePoint-synced files from Finder after macOS Tahoe 26.6 update
Files stored in SharePoint Online and synchronized locally through OneDrive are opened as local documents when launched from Finder. Office applications display "Saved to my Mac" and AutoSave is turned off by default. However, opening the exact same files through Word/Excel > Open > Sites, or via SharePoint "Open in Desktop App", correctly identifies them as cloud documents. In that scenario, AutoSave is enabled and collaboration/version history features work as expected. Troubleshooting already performed: OneDrive reset and re-linked SharePoint library re-synced Signed out and back into both Office and OneDrive Removed Microsoft credentials from macOS Keychain and re-authenticated Recreated local OneDrive sync relationships Verified OneDrive File Provider extensions are enabled Verified Office applications and OneDrive are fully up to date Tested with newly created files and existing files Tested "Always Keep on This Device" with no change in behavior The issue appears to be specific to the Finder-to-Office launch path after upgrading to macOS Tahoe 26.6. Before upgrading to macOS Tahoe 26.6, opening the same SharePoint-synchronized files directly from Finder correctly preserved cloud document identity and AutoSave was enabled as expected. I discussed this issue in detail with Apple Support, but they quickly dismissed it, saying that the problem is not on Apple's side and that I should contact Microsoft instead.
Bug Report: Sudden failure of OneNote Web automatic color rendering
Context: OS: Mac OS Web Browser: Google Chrome Color Theme/Mode: Dark Mode (across OS, browser, and apps where available) OneNote for the web has suddenly started failing to properly display automatic color. For a long time, I've used OneNote across web, desktop, and mobile. For desktop and mobile I've enjoyed dark mode color theme. For web, and explicit dark mode setting has not been available — and the system/browser dark mode setting has had no effect. Normal text, (especially one whose color is set to "automatic" by default), it would always render properly across all the environments, including the effectively light mode web and dark mode desktop/mobile. Since a few days ago, the OneNote web has developed a weird bug. On one hand, the UI elements have turned dark (as if dark mode was available and enabled). On the other hand, the actual notes area has a background that appears white — while the (automatically colored) text color appears very light gray — practically invisible. It's as if OneNote web went through a partial dark mode transformation. UI has dark mode, notes background is in light mode, yet the actual text behaves as if it's also in dark mode. The light-on-light text then is effectively invisible. Desktop and mobile apps work fine. Bug appears on a different browser (Mozilla Firefox; mode=dark) as well. Bug has been reported to customer support and confirmed as internally logged.
Importing ICS to selected calendar
I want to import an ICS into a new or selected Outlook calendar that is not my default calendar. I've been reading up and have yet to find a solution. The only two ways I have found are both awkward: 1) import into the default calendar and then use List view to select the ones you just imported ("if" you can isolate them all with a given search term) and then cut and paste or drag into the desired calendar, or 2) change the default calendar in account settings to do the import and then change it back. There has to be a better way. Thanks!
Unlocking Microsoft 365 Adoption in Engineering, Manufacturing, and Regulated Industries
Executive Feedback to Microsoft Leadership: Expanding the Value of Microsoft 365 Beyond Cloud-First Workflows Executive Summary Microsoft has successfully built the industry's leading cloud collaboration ecosystem around Microsoft 365, OneDrive, and SharePoint. The strategy has delivered substantial value for information workers, distributed teams, and organizations pursuing cloud-first operating models. However, there is a significant and often overlooked customer segment that remains underserved: engineering, manufacturing, healthcare, medical device, industrial, laboratory, defense, and other regulated organizations whose primary workflows are intentionally built around file-based repositories, network shares, PDM/PLM systems, and controlled document environments. The challenge is not opposition to cloud technology. The challenge is that many of these organizations prioritize data integrity, traceability, predictability, and workflow continuity above all else. As a result, they often perceive modern Microsoft productivity capabilities such as AutoSave, coauthoring, and version history as being unnecessarily coupled to OneDrive and SharePoint. This creates an important business opportunity. Microsoft could unlock substantial additional Microsoft 365 adoption and customer goodwill by extending modern document protection and collaboration capabilities to local, network-hosted, and hybrid file environments without requiring a complete migration to OneDrive or SharePoint. This is not a request to replace cloud services. It is a request to recognize that cloud-first and file-based workflows can coexist. The Opportunity Is Larger Than It Appears Many of Microsoft's largest enterprise customers operate in environments where files are not simply documents. They are: Design history files Manufacturing records Engineering drawings Validation reports Device master records Controlled procedures Laboratory data Regulatory submissions Quality records For these organizations, file location, revision control, ownership, auditability, and retention are operational requirements rather than convenience features. Microsoft itself acknowledges that Office AutoSave currently requires files to be stored in OneDrive or SharePoint. Files opened from traditional file-system locations do not receive the same experience. As a result, many organizations feel they must choose between: Maintaining proven operational workflows. Accessing Microsoft's most advanced productivity features. That is a business decision many organizations simply refuse to make. The Real Barrier Is Not Technology. It Is Trust. Discussions around cloud adoption are often framed as a resistance-to-change problem. Research consistently suggests otherwise. Studies examining enterprise cloud adoption repeatedly identify security concerns, data privacy concerns, and control over organizational information as major barriers to adoption. One study found security concerns dramatically increased the likelihood that organizations would reject cloud adoption. Similarly, KPMG's cloud transformation research notes that concerns about data loss, audit findings, compliance issues, and operational risk can slow or limit cloud initiatives. The lesson is important: Organizations rarely reject technology because it is new. They reject technology because they do not trust it with critical business information. Once users experience: unexpected file overwrites, synchronization ambiguity, permission confusion, data residency uncertainty, conflicting document versions, trust declines rapidly. Trust, not functionality, is often the limiting factor. Engineering Users Experience the World Differently Microsoft's cloud ecosystem was largely designed around information-worker collaboration. Engineering organizations frequently operate under different assumptions: Information Worker Priority Engineering Priority Seamless sharing Data integrity Anywhere access Traceability Real-time collaboration Configuration control Ease of use Auditability Cloud accessibility Revision certainty Neither approach is wrong. The challenge is that Microsoft increasingly optimizes for one while under-serving the other. An Example: AutoSave AutoSave is one of the most valuable additions Microsoft has made to Office. The value proposition is obvious: Reduced data loss Improved productivity Lower cognitive burden Better user confidence Microsoft's own documentation describes AutoSave as continuously saving changes while users work, but only when documents reside in OneDrive or SharePoint. From Microsoft's perspective, this design is understandable. From the customer perspective, the message often becomes: "Modern document protection is available, but only if you adopt Microsoft's preferred storage architecture." Many customers view this not as a technical limitation, but as product segmentation. Microsoft Could Learn from Version Control Systems Modern software development solved multi-user document conflicts decades ago. Git was specifically designed around realities such as: multiple devices, multiple contributors, offline work, concurrent editing, conflicting changes. Critically, Git assumes conflicts are inevitable. Rather than hiding them, Git exposes conflicts and provides mechanisms to resolve them. Many engineers trust Git precisely because its behavior is transparent. By comparison, file synchronization systems often attempt to abstract away complexity. When synchronization fails, users can no longer determine: which version is authoritative, which edits are newer, what happened, who changed what. The engineering mindset is frequently: Show me the conflict. rather than Hide the conflict and make a decision on my behalf. The Untapped Hybrid Customer Much discussion around Microsoft 365 assumes organizations are either: Cloud-first, or Legacy. In reality, many enterprises are neither. Many operate as hybrid organizations and intentionally will continue to do so. Research from industry and security organizations continues to show persistent adoption of hybrid and multi-cloud architectures driven by governance, security, compliance, and operational requirements. These customers are not rejecting Microsoft. They are already paying customers. They often purchase: Microsoft 365 Windows Azure Teams Active Directory SQL Server Yet many would immediately purchase additional capabilities if Microsoft offered: Local AutoSave Office AutoSave functionality for: NTFS local storage SMB file shares NAS systems PDM-managed documents Local Version History Built-in document time travel without cloud dependence. Hybrid Collaboration Coauthoring capabilities that operate through enterprise file infrastructure. Enterprise Conflict Resolution Visualization and reconciliation of competing document changes. Network-Aware Document Protection The same confidence users experience in OneDrive without requiring migration to OneDrive. The Revenue Opportunity This is not merely a product-improvement request. It is a business opportunity. A significant portion of engineering and regulated industries remain hesitant to migrate entirely into cloud-centric document ecosystems because the perceived operational risks exceed the perceived benefits. Rather than forcing an all-or-nothing decision, Microsoft could monetize a middle path: Microsoft 365 Hybrid Collaboration A premium offering delivering: AutoSave Version History Recovery Conflict Resolution Audit Visibility for enterprise-controlled file infrastructure. Organizations that decline OneDrive adoption today may still eagerly purchase these capabilities. In effect, Microsoft could create incremental revenue from customers who are already committed to the Microsoft ecosystem but currently feel underserved by a cloud-only feature strategy. Recommendation Microsoft should stop treating file-server and network-share users as transitional users waiting to migrate. Many are not transitioning. Many have intentionally chosen architectures optimized for regulatory compliance, engineering rigor, operational control, and data governance. The future should not require choosing between: modern productivity features, and trusted enterprise workflows. The organizations building medical devices, industrial equipment, aerospace systems, manufacturing infrastructure, energy systems, and critical technologies represent some of Microsoft's most technically sophisticated and commercially valuable customers. They deserve first-class support for the workflows they intentionally operate. The opportunity is not to move every customer to the cloud. The opportunity is to bring Microsoft's best innovations to every customer, regardless of where their files live.
Disable incessant nagware popups
I don't know about everyone else, but I am sick and tired of the nagware pop ups in Word, Excel, PowerPoint, Outlook, etc. Every single product harasses me with pop ups trying to tell me "hey, did you know this feature was here?", "you can do this if you click that", "let me hold your hand through using products you've used for decades even though you don't want daddy Microslop to do that". This is a prime example. I keep getting the same ones again and again and again and everything I've read indicates they should only appear once. But they don't. They keep coming back like a psychotic stalker ex who wants alimony even though you were never married. How do I get this nagware to stop?!No acces to local Office365 apps with an account which differs from the current windows account
Hi, guys! I'm working with Windows 11 Pro using the Microsoft account ABC. Today I bought a Office 365 Family License - by using another Microsoft account XYZ. I downloaded the local apps successfully... ...but when I start the local app and tried to sign in using the XYZ account, I'm asked for the Windows Hello Pin for the XYZ account - but there is no PIN for that, because the account doesn't exist as a Windows account at this computer at all. Copilot says: "You can sign in to Windows 11 with one Microsoft account and use a different Microsoft 365/Office account for Office applications. Microsoft supports this setup." What did I wrong - what can I do? Kind regards! Sebastian
Planning a Google Workspace to Microsoft 365 Migration? What Should You Consider?
Hi everyone, Has anyone recently migrated from Google Workspace to Microsoft 365? I’m interested in knowing what challenges you faced during the migration, especially around mailbox data, calendars, contacts, user mapping, or the final cutover process. For those planning the migration, what are the key things you recommend preparing before getting started? Would like to hear your experiences and suggestions.New Family Subscription: Flexibility is nice, axing storage (5=>2 TB) is NOT
As you likely all know, MS just announced to change the storage model for Office 365 family subscriptions. Instead of having 5 users with 1TB each there will be 2TB shared space. The email announcement did not talk about families that use more than 2TB. In a chat with the support I just learned: The new flexibilty is nice... but axing storage more than half is terrible! What makes it even worse is that neither I nor ChatGPT could find information what it will cost if I want to continue using 5TB. I do understand that prices are increased from time to time. But making it so shady and intransparent is not what I would expect from a firm like MS...
