Forum Widgets
Latest Discussions
Welcome to the new Office End of Support community!
This community will provide a forum to discuss topics related to the end of support for all Office client products, including key dates to be aware of, recommended upgrade paths, support resources, and technical details spanning all affected audiences. Microsoft is dedicated to helping businesses and individuals succeed by empowering them to work together seamlessly, from anywhere. Most Microsoft products have support lifecycles during which we provide bug fixes and security fixes. The end of this lifecycle is known as the product's end of support. When a product reaches the end of support, Microsoft no longer provides the following: Technical support for issues Bug fixes for issues that are discovered Security fixes for vulnerabilities that are discovered As end of support deadlines approach, Microsoft strongly recommends users shift to newer software to help them stay productive, safe, and at the forefront of digital transformation. Want to stay in touch? Click “Join” to ensure you get all the latest news and information about changes to Office support in the coming months.Support for Office 2010—and Office 2016 for Mac—has ended: Here’s what you need to know
On October 13, we marked theend of support for Office 2010and Office 2016 for Mac. This means that we’ll no longer provide technical support, bug fixes, or security updates for these products, and organizations that continue to use them may face increased security risks and compliance issues over time. The requirements for connecting to Office 365 serviceshave also changed—and customers will now need Microsoft 365 Apps, Office 2019, or Office2016toconnect to Office 365 serviceslike Exchange Online and SharePoint Online. While we will not take any active measures to block legacy versions of the Office client from connecting, these older clients will fall out of step with the service enhancements and may present performance and/or reliability issues over time. Read the full announcement of these changes here.
Office 2019 users getting error when opening files in app from sharepoint
Hi, since two days ago, our users who didnt upgrade to office 365 and still use office 2019 are getting an error when trying to sign in from office to their cloud account. The error is: "Your account is in bad state. Please sign-in to this account online to address the issue" Now I know support for cloud connectivity for office 2019 has officially ended in october 10, two days ago, in microsoft website its stated that: "In practical terms, what this means is that older Office versions might not be able to use all the latest functionality and features of Microsoft 365 services... No active measures will be made to block older Office versions from connecting to Microsoft 365 services if they're in extended support and are kept up to date. For example, Office 2019 and Office 2016, both of which are in extended support until October 14, 2025."Office versions and connectivity to Microsoft 365 services - Deploy Office | Microsoft Learn So why it looks like Microsoft actively blocked office 2019 connection to cloud?
Windows Server 2022 and M365
I'm looking at the Win and Office support matrix and Win Server 2022 and M365 Apps aren't supported. Can anyone explain why this is? It looks like Microsoft if going to remove the ability to host virtual desktop for clients and install M365 licensing on it. I assume in a push forcing people to use Azure.MS office 2016 perpetual Volume Licenses Queries
Hi , pl help me to get clarification of following points :- How do we find the number of activation done against one MAK (Multiple Activation Key) Volume Licenses –Office 2016 What is the maximum number of activation allowed on a volume licenses- say the key for 100 licenses. Reallocation of volume licenses - Can we disable the volume licenses from one machine and activate it in another in case the user is changing the laptops. if yes steps to be followed. regards AC
Workflow 2013 Deprecation
As mentioned in the following article: https://techcommunity.microsoft.com/t5/office-end-of-support-blog/support-update-for-sharepoint-2010-workflows-in-microsoft-365/ba-p/1505453 Workflow 2013 will become deprecated in the near future. When workflow 2013 will reach end of support, does this also mean that the related content type 'Workflow Task (SharePoint 2013)' will be deleted? How will this work? This would not be desired in some cases, because maybe we would want the new power automate to use the same data structure for their tasks. In that case, we could still reuse the same content type which reduces the impact of the rework. Also, there is a lot of historical data for us in these workflow tasks (or a content type that inherits from 'Workflow Task (SharePoint 2013)'), deleting the content type would mess up this historical data. With kind regards, Stijn Brouwers
Office 365 ProPlus version out of support implications
We have Office 365Semi-Annual Enterprise Channel 1902, which goes out of support onSeptember 8, 2020. After that date Microsoft have published that we will get no more Technical Support for issues, bug fixes or security fixes. However is there any published Microsoft information on connectivity to Office 365 Services? The only links I can find are ambiguous as to whether the "in mainstream support" phrase applies to Office 365 ProPlus or just Office Perpetual clients: https://techcommunity.microsoft.com/t5/office-365-blog/office-365-system-requirements-changes-for-office-client/ba-p/62327 https://www.microsoft.com/en-us/microsoft-365/blog/2018/09/06/helping-customers-shift-to-a-modern-desktop/Skype for Business client on Office 365 suite
Hi, Anybody could share what happen to Skype for Business client on Office 365 suite when Skype for Business online is going to be end at 2021? Will that become end of lifecycle as well and be removed from the suite. Asking this because we and perhaps others as well might use that package to on-premises Skype for Business environment.
