![]() Starting with the November 2022 update (16.67) macOS Big Sur 11 or later is required to receive updates to Word, Excel, PowerPoint, Outlook, and OneNote. We recommend that you upgrade to Microsoft 365 for Mac or Office 2021 for Mac. Important: Support for Office 2019 for Mac will end on October 10th, 2023. ![]() If you continue with an older version of macOS, your Office apps will still work, but you'll no longer receive any updates including security updates. Starting with the November 2022 update (16.67) macOS Big Sur 11 or later is required to receive updates to Word, Excel, PowerPoint, Outlook and OneNote. OneDrive: Select Send Feedback from the Help & Settings tab. ![]() Outlook: Select Contact Support from the Help menu. Word, Excel, PowerPoint and OneNote: Select the Feedback icon in the top-right corner of the app. ![]() If you encounter any issues while using Office, please send us feedback so we can address them. For the best experience with the new operating system, make sure that you have installed the latest updates for Word, Excel, PowerPoint, Outlook and OneNote. For example, if you’re on macOS Big Sur 11, but later you don’t update your macOS to a supported version when macOS Big Sur 11 is no longer supported, you won’t receive any updates of any kind.Īs new major versions of macOS are released and older versions become unsupported, we highly recommend you continue to update your macOS to a supported version in order to receive mainstream support such as security updates as well as new features. If you’re on an unsupported version of macOS, your Office apps will still work but you would no longer receive any updates including security updates. What if I don't update macOS to a supported version? Learn more about the latest macOS releases. The October 2022 update (16.66) is the last build to support macOS Catalina 10.15. Note that new installs of Microsoft 365 for Mac also requires macOS Big Sur 11 or later. Upgrading your operating system to macOS Big Sur 11 or later will allow Office updates to be delivered for your apps. I was asking about some sort of standard link for download to see if I could re-write the AutoPKG recipe, but understand what you're saying about the statics.Starting with the November 2022 update (16.67) macOS Big Sur 11 or later is required to receive updates to Word, Excel, PowerPoint, Outlook, OneNote, and Microsoft Defender. ![]() Eventually Microsoft linked to this Jamfnation post and said to download the latest version using your link, and later they grudgingly agreed that it's kind of an interim update and that downloading the publicly-available PKG and then relying on autoupdate to update it to the latest version would be fine. When I downloaded it and looked at the installer PKG with Suspicious PKG it was still the version that AutoPKG found. I asked them if the "newest" version they recommended was some sort of an interim update (where it could only be obtained through autoupdate and wasn't available as a standalone PKG) and they said no and sent me a link to their public Teams download site. We normally use AutoPKG with a Teams recipe, and when I ran that it didn't find any newer version that what was already there. We had been dealing with a support ticket with Microsoft Support regarding Teams, and they kept telling us we had to get the latest version of Teams in Jamf. I've been finding recently that a new Team's release can show up randomly on our environment up to 2 weeks before its listed as a download under macadmin.software as a GA releaseĪs we have no control over when our user get this push directly from Microsoft via the Teams automatic update, we take lead and use Jamf patch management to force the update to all users so they are all on the same version as soon as we know its released into the thanks for your response. If you then take this version number reported in "unknown" just change the number within the URL to match to get the link for this release. The repositories only get created when there's a new slow or fast insider build of Teams but I have not found any documentation of when Microsoft decide to make a build available or take one of these builds and mark its release as a final build.Īs we don't allow Slow or Fast Insider builds in our production environment, we do know that if we see jamf patch reporting a "unknown" version and this version is higher that listed in patch management, then this is a build that has been released by Microsoft themselves to our our fleet. ![]()
0 Comments
Leave a Reply. |