office 365
20753 TopicsAutoSave 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.7Views0likes0CommentsHVE for Microsoft 365: When to Use It, When Not To, and Who Should Be Allowed to Send at Scale
Microsoft recently announced the General Availability of High Volume Email for Microsoft 365, also known as HVE, in Exchange Online. This is an important and long-awaited capability for organizations that need to send large volumes of internal email from applications, devices, or line-of-business systems without using regular user mailboxes as bulk-sending engines. But HVE should not be misunderstood. It does not mean that every mailbox in Exchange Online should now be used for mass email. It does not mean Exchange Online has become a general-purpose marketing platform. And it does not remove the need for proper outbound email governance. Why HVE Matters For years, many organizations have used regular Exchange Online mailboxes, shared mailboxes, or service accounts to send automated messages from applications, scanners, monitoring platforms, ticketing platforms, and custom business applications. That approach creates several problems. Standard mailboxes are designed for human and business communication, not for sustained high-volume automated traffic. Exchange Online has recipient limits, message rate limits, outbound spam protections, and tenant-level controls to protect the service and reduce abuse. HVE introduces a more appropriate model for specific high-volume scenarios. Instead of using a normal mailbox for automated traffic, organizations can create dedicated HVE accounts and use specific SMTP endpoints, admin controls, reporting, and governance for approved high-volume internal messaging scenarios. What HVE Is Designed For HVE is designed for automated, operational, and transactional messaging at scale, primarily for internal recipients within the tenant. Examples include: Internal application notifications. Line-of-business system messages. Device-generated messages. Operational alerts. Security advisories. Internal workflow communications. Monitoring platform alerts. IT service notifications. Large-scale internal announcements generated by systems. This is especially relevant when the organization needs to send messages at scale but still wants to keep the workload within Microsoft 365 governance and Exchange Online mail flow. In practical terms, HVE is useful when the sender is not a human user, but a controlled business system. What HVE Is Not HVE is not a replacement for marketing platforms. HVE is not a general-purpose internet bulk email engine. HVE is not a way to bypass Exchange Online sending limits for external campaigns. HVE is not the correct platform for newsletters, promotional campaigns, large-scale customer communication, or high-volume external transactional email. For external transactional, marketing, or customer-facing bulk email, organizations should evaluate platforms designed for that purpose, such as Azure Communication Services Email, SendGrid, Amazon SES, Mailchimp, Brevo, or another specialized delivery platform. When to Use HVE Use HVE when the workload matches these characteristics: The sender is an application, device, service, or business system. The recipients are primarily internal users in the Microsoft 365 tenant. The volume is higher than what should be sent from a standard mailbox. The workload is operational, automated, or transactional. The organization needs centralized Microsoft 365 administration and reporting. The organization wants to avoid impacting user mailbox sending limits. The use case is approved, documented, monitored, and governed. Good examples: A security platform sending internal security advisories. A monitoring system sending infrastructure alerts to internal teams. A business workflow system sending high-volume approval or status notifications. An IT service platform sending internal notifications. A service management platform sending ticket updates to internal users. A device management system sending operational messages to internal teams. When Not to Use HVE Do not use HVE when the workload is external bulk email. Avoid HVE for: Marketing campaigns. Newsletters to customers. Promotional email. Mass external invitations. External transactional email at scale. Customer invoices and receipts in high volume. OTP or password reset flows for external users. External portal notifications. Any workload where deliverability, bounce handling, reputation management, unsubscribe handling, analytics, or customer consent management are required. Those workloads require a platform designed for external delivery, reputation management, suppression lists, opt-out, tracking, bounce handling, and compliance. Who Should Be Allowed to Use HVE HVE should not be enabled casually for every team or every application. It should be treated as a controlled platform capability. Recommended eligible senders: Approved line-of-business applications. Corporate systems owned by IT, Security, Operations, Facilities, or Service Management teams. Managed devices or services with a clear business purpose. Internal platforms that send operational messages to employees. Applications with documented ownership, authentication, monitoring, and expected volume. Recommended non-eligible senders: Normal users. Shared mailboxes used by humans. Marketing teams sending to external audiences. Unmanaged scripts. Legacy systems with no owner. Applications with unknown volume. Systems that send to external recipients at scale. Any application using HVE just to avoid standard mailbox limits. The core principle is simple: HVE should be enabled for workloads, not for convenience. Governance Model Before enabling HVE, organizations should define a governance model. At minimum, each HVE account should have: A named business owner. A technical owner. A documented purpose. Expected daily and monthly volume. Recipient scope. Authentication method. Monitoring process. Incident response path. Decommissioning criteria. Review frequency. HVE accounts should not become invisible service accounts that nobody owns. They should be treated as privileged communication identities. Security and Authentication HVE supports OAuth authentication, and Microsoft provides guidance for restricting OAuth authentication to specific Microsoft Entra ID applications. This is important because organizations should avoid broad, uncontrolled access. They should restrict which applications can send through each HVE account, monitor usage, and separate workloads by purpose. For example: One HVE account for security alerts. One HVE account for monitoring systems. One HVE account for IT service notifications. One HVE account for internal operational communications. This separation improves visibility, investigation, accountability, and risk containment. HVE vs Standard Exchange Online Mailboxes A standard Exchange Online mailbox should be used for normal human communication. A shared mailbox should be used for collaborative business processes. An HVE account should be used for approved high-volume internal system email. A dedicated external delivery platform should be used for marketing, bulk external communication, or high-volume transactional email. Scenario Recommended Platform Human business email Exchange Online mailbox Team or department mailbox Shared mailbox Low-volume application notifications Standard Exchange Online, if approved High-volume internal system notifications HVE Internal operational alerts at scale HVE Marketing campaigns Marketing platform External transactional email Transactional email service Customer newsletters Marketing automation platform OTP/password reset for external users Dedicated transactional platform External bulk email Dedicated bulk email provider HVE and the Mailbox External Recipient Rate Limit Cancellation Microsoft also announced that the Mailbox External Recipient Rate Limit in Exchange Online was cancelled indefinitely. However, that cancellation should not be interpreted as permission to use Exchange Online for uncontrolled bulk sending. Microsoft was clear that other limits remain unchanged, including the existing Recipient Rate Limit and the Tenant-level External Recipient Rate Limit. That distinction is important. The cancellation of one mailbox-level external recipient limit does not remove the need for proper architecture. Exchange Online still has service limits. Outbound spam controls still apply. Tenant-level protections still matter. And HVE is still not a marketing engine. Practical Architecture Decision Before enabling HVE, ask these questions: Who is sending? Is the sender a human, shared mailbox, application, or device? Who are the recipients? Are they internal or external? What is the expected volume? Is the workload operational, transactional, promotional, or human communication? Does the business need Microsoft 365 mail flow and governance? Does the use case require bounce handling, unsubscribe, tracking, or reputation management? Is the application properly authenticated and monitored? Who owns the account? Who approves the sending pattern? Who responds if the account is abused? If the workload is internal, automated, high-volume, and business-approved, HVE may be the right answer. If the workload is external, promotional, customer-facing, or marketing-driven, use a dedicated email delivery platform. Recommended Enablement Approach Organizations should enable HVE in phases. First, identify existing systems currently using user mailboxes, shared mailboxes, or SMTP AUTH for automated sending. Second, classify each workload as internal, external, operational, transactional, marketing, or human communication. Third, migrate only approved internal high-volume workloads to HVE. Fourth, move external high-volume workloads to dedicated email delivery platforms. Fifth, monitor usage and review HVE accounts regularly. This avoids turning HVE into another uncontrolled sending layer. Conclusion High Volume Email for Microsoft 365 is an important addition to Exchange Online. It gives organizations a native way to support high-volume internal system messaging without using standard mailboxes for automated high-volume traffic. But HVE is not a free pass for bulk email. It is not a marketing platform. It is not a replacement for transactional email services. And it should not be enabled for every mailbox or every application. The right approach is workload classification. Use Exchange Online for corporate communication. Use HVE for approved high-volume internal system messaging. Use dedicated platforms for external bulk, marketing, and transactional email. The question is not only: “Can this system send email through Microsoft 365?” The better architectural question is: “What type of email is this, who is the audience, and what is the correct platform for this workload?” That is where proper email architecture begins.386Views0likes3Comments# OneDrive AutoSave Stopped Working After Update to Version 26.007.0112 on macOS
**Product:** Microsoft 365 and Office | OneDrive | For home | macOS ## Summary Since OneDrive automatically updated to version 26.007.0112 (26007.0112.0002) a few days ago, I am experiencing multiple issues with how Office files interact with OneDrive on my Mac. AutoSave no longer works, files that are stored locally now take noticeably longer to open, and attempting to work around the problem through Word/Excel directly results in upload failures and outdated file versions. Prior to this update, everything was working perfectly. ## Environment - **macOS version:** Tahoe 26.1 - **OneDrive version:** 26.007.0112 (26007.0112.0002) - **Office version:** Version 16.105.2 (26012530) - **Account type:** Business ## Symptoms ### 1. AutoSave no longer activates when opening files from Finder Opening any .docx or .xlsx file from the OneDrive folder in Finder results in AutoSave being off. The title bar shows "Saved on My Mac" instead of the OneDrive location. Attempting to toggle AutoSave on prompts me to "upload" the file — even though it is already in the OneDrive sync folder and marked as "Always Keep on This Device." ### 2. Files that are stored locally now open slowly Previously, opening an Office file from the OneDrive folder in Finder was instantaneous, as you would expect for a file stored on the local drive. Now, even though the files are marked as "Always Keep on This Device" and should be fully available locally, there is a noticeable delay when opening them. It appears that OneDrive or the Office app is downloading or re-fetching the file from the cloud rather than simply opening the local copy, which defeats the entire purpose of keeping files on the device. ### 3. Opening from within Word/Excel results in "Upload Failed" and serves an older version As a workaround, I tried opening files from within Word using File > Open and selecting the OneDrive location. However, this now produces an "Upload Failed" error message, and the file that opens is an older version — not the most recent version I had been working on. This is extremely concerning, as it suggests the sync between the local copy and the cloud copy may be broken, and there is a real risk of data loss or overwriting recent work with outdated content. ## Steps to Reproduce 1. Ensure files are in the OneDrive folder and marked as "Always Keep on This Device." 2. Open a .docx or .xlsx file by double-clicking it in Finder. Notice: the file takes several seconds to open (previously instant), AutoSave is off, and the title bar says "Saved on My Mac." 3. Close the file. Open Word or Excel, go to File > Open, and navigate to the OneDrive location. Open the same file. Notice: an "Upload Failed" message appears, and the file that opens is an older version, not the most recent one. ## Expected Behavior - Files stored locally via "Always Keep on This Device" should open instantly, just as any local file would. - AutoSave should be enabled automatically when opening files from the synced OneDrive folder. - Opening a file from within Word/Excel via the OneDrive location should open the current version of the file without upload errors. All of this worked exactly as expected before the update to version 26.007. ## What I've Tried - Verified that "Always Keep on This Device" is enabled for the affected folders. - Confirmed I am signed into the same Microsoft account in both OneDrive and the Office apps. - Verified files are in modern formats (.docx, .xlsx), not legacy formats. - Checked that OneDrive sync is not paused. ## Impact This is a severe workflow disruption. The combination of broken AutoSave, slow file access, and the "Upload Failed" error serving stale file versions means I cannot trust that I am working on the latest copy of my documents. There is a genuine risk of data loss — if the cloud version is out of sync with the local version, saving could overwrite recent work with an older copy. I am currently unable to rely on OneDrive for day-to-day work on my Mac. ## Additional Notes This appears to be a regression introduced by the recent OneDrive update to version 26.007. I have seen numerous other users reporting similar AutoSave and sync issues across Microsoft Q&A, Apple Community forums, and MacRumors, dating back to the original Files On-Demand changes on macOS. However, my setup was working correctly until this latest update. Relevant threads with related issues: - https://learn.microsoft.com/en-us/answers/questions/5419331/onedrive-says-saved-on-mac-autosave-not-working - https://learn.microsoft.com/en-us/answers/questions/5371608/one-drive-auto-save-no-longer-working-on-mac-os - https://learn.microsoft.com/en-us/answers/questions/5402091/onedrive-app-on-mac-not-working-for-autosave-and-t - https://forums.macrumors.com/threads/onedrive-autosave-disabled-when-opening-files-from-onedrive-folder.2442775/ I would appreciate any guidance from the community or the Microsoft team. Is this a known regression in version 26.007? Is a fix in progress? Is there a way to roll back to a previous OneDrive version that was working? Thank you.887Views3likes3CommentsFile Save As takes 20-30 seconds for Dialogue to appear
Latest Feature Update & Quality Update of Windows 10 21H1 Latest Update of Microsoft 365 / Office 365 - Excel We have a customer complaining that their PC is running slow, he is a heavy user of Excel. Upon investigation it was determined that the problem appears to be that when he tries to save or Save as an existing or new Excel Workbook, it takes 20-30 seconds for the Dialogue to save or Save as to appear. This is a domain joined PC, with a number of mapped drives, One Drive configured. The testing conducted are as follows: Trying to Save As an Existing or NEW Workbook even with one single cell with data in it - takes up to 30 seconds for the dialogue to enter the location and file name to appear Removed ALL Recent Files from the Recent List - No Change Ran the Office Repair from Control Panel - No Change Un-Install Office - Using Microsoft Office Removal Tool Re-Install Office from Scratch - No Change Logon as a different user to the current user - Works OK, takes a few seconds for the Dialogue to appear. Seems to be User Profile related, it seems like one other user is having the same problem, no other users are complaining of this. The next step is going to be to re-install Windows 10 which seems a bit over the top. If anyone has any ideas?3.1KViews0likes3CommentsIs it possible to do this?
Hey all! I currently use Smartsheet to track my trainees' progress and I love the way I can use Conditional Formatting in that program. Unfortunately, my company is going away from using Smartsheet, so I need to move all the information I have to an Excel document. I'm struggling with getting the Conditional Formatting to work the same way I have it in Smartsheet and I'm curious if it's even possible. Here is an image of the Template I will be using for each employee. My plan is to have a tab for each employee, just duplicating the template and renaming it to their name and adding their information. Here are the two things I'm struggling with getting set-up with Conditional Formatting: 1. In the Lvl column, I have a drop down that is linked to the Data tab where the icons on the left are images. I want to be able to select the "Assigned" option and have the A icon show up (this is currently set up) and then have the fill of the box turn to red. I'm struggling to get that to work properly. Currently, when I select the "Assigned" option in the drop-down menu, it just shows the "A" icon. 2. I also want to be able to have the "Date Completed" column change to a specific color if one of the checkbox columns (G, H, I, J, K) are checked (i.e. if G is checked, it turns a light brown, if H is checked, it's gray, if I is checked, then it's red, etc.). This is what it looks like in Smartsheet and how I'm hoping to get it to look in Excel: Thank you!6Views0likes0CommentsOneDrive suddenly became empty after university storage policy change Is recovery still possible?
Hello everyone, I am looking for technical guidance regarding a serious OneDrive for Business issue under Microsoft 365 Education. Environment - Microsoft 365 Education tenant. - University-managed account. - OneDrive for Business. - My account is still active and I can sign in normally. What happened On July 16, 2026, I signed into my OneDrive and discovered that my entire "My files" folder was empty. I verified the following: - I am signed into the correct account. - "My files" is completely empty. - The OneDrive Recycle Bin is empty. - "Restore your OneDrive" does not show any mass deletion event. - My OneDrive site is accessible, but there are no files. - I unfortunately do not have a complete local backup. A few days later, my university informed students that they had reduced the OneDrive storage quota from 5 TB to 30 GB due to a Microsoft/provider policy update. I suspect my OneDrive contained more than 30 GB because I had stored backups from my previous computer together with years of academic, personal and work files. However, I would like to understand whether exceeding the new storage quota could actually cause an existing OneDrive site to appear completely empty, or whether this suggests another issue such as: - OneDrive reprovisioning - Site replacement - License reassignment - Site deletion - Storage migration - SharePoint issue - Other administrative problem The university initially described this as a temporary Microsoft incident, but later told me that the files had been deleted because of the OneDrive application, without providing any technical explanation. I have already asked the university IT department to investigate: - Deleted Sites in SharePoint Admin Center - Second-stage Recycle Bin - Retention policies - Previous OneDrive site - Licensing history - Possible restore options My question to Microsoft experts is: 1. Can a storage quota reduction (5 TB → 30 GB) ever make an existing OneDrive appear completely empty? 2. Are there other administrative scenarios that could produce this behavior while leaving the account active? 3. Is there anything specific I should ask my Microsoft 365 administrator to verify that is commonly overlooked? Any guidance would be greatly appreciated because these files represent several years of academic, professional and personal work. Thank you very much.7Views0likes0CommentsHow to share calendar from Shared mailbox to mobile app
Hi, In our organization, we have the following requirement: to create three calendars within a shared mailbox and make them visible to members on both PC and the mobile app. On the PC, they are visible, but not on the Outlook app. On the app, we can only see the main shared mailbox calendar, not the three additional ones. The goal is to visually distinguish the three types of appointments on the app. We tried using categories (tags), but the colors have to be reset for each member. Any suggestions? Thanks37Views0likes2CommentsHow 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.Excel Suddenly slow saving
Excel for Office 365 16.0.12527.22049 64-bit Windows 7 and Windows 10 We have two workbooks that are templates. One is used for around 150+ projects a year. This workbook has the issue. The second workbook is a similar template that is used for about 50 projects a year. This workbook does not have the issue. Problem: When saving a workbook using the one template that is used for 150+ projects/Yr, the save now takes 7 to 10 minutes with the "Saving (Not Responding)" message. This just started on Friday 11/26/2021. The day before there were no issues. Workbooks from this template that had previously saved quickly no longer save quickly. Workbooks from the other template continue to work correctly. There does not appear to have been any updates applied to the system. This is happening to all users with workbooks based on the one template, but not the other. The workbooks started from similar designs and use similar operations. They both have 75+ very hidden data tables used for dropdowns. The data tables query a SQL DB. HLookups and VLookups are used. There are several hundred field names. There is an Excel Add-in containing numerous functions. There is also a third-party VSTO add-in. This cannot be turned off (except maybe running in save mode). There are no external linked files. Have tried: Turning off Automatic workbook calculation and turned off Recalculate workbook before saving – No help Disabled add-ins – no help Moved project files to local drive – no help Ran Excel in Safe Mode - No help Workstations and Server have been restarted - No Help Deleted tabs until problem went away. Did not get narrowed down to a single tab. Seems to be a combination somewhere among about 15 tabs. Moved project files to local drive and removed workstation from network – problem goes away. The remaining tabs use a lot of the same advanced formulas. Since the problem goes away when not attached to the network, I did not attach the workbook. The workbook is basically the work product for our business, so the whole thing is pretty proprietary. At a complete loss as to what to look at next.25KViews0likes8Comments