Merge branch 'main' into kainawroth-auto-vm

Author: kainawroth

.openpublishing.redirection.exchange.json

@@ -4,6 +4,10 @@
  "source_path": "Exchange/ExchangeOnline/mobile-devices/outlook-app-access-end-after-june-1-if-ews-app-policies-not-set-correctly.md",
  "redirect_url": "/previous-versions/troubleshoot/exchange/exchangeonline/outlook-app-access-end-after-june-1-if-ews-app-policies-not-set-correctly"
  },
+ {
+ "source_path": "Exchange/ExchangeServer/Administration/exchange-2013-end-of-support.md",
+ "redirect_url": "exchange-2016-2019-end-of-support"
+ },
  {
  "source_path": "Exchange/ExchangeOnline/outlook-on-the-web-issues/archive-mailbox-not-visible.md",
  "redirect_url": "/troubleshoot/outlook/profiles-and-accounts/archive-mailbox-not-visible"

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
  "redirections": [
+ {
+ "source_path": "support/windows-client/windows-tss/gather-information-using-tss-sql-cluster-ag-fci-issues.md",
+ "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-sql-cluster-ag-fci-scenarios",
+ "redirect_document_id": false
+ },
  {
  "source_path": "support/azure/virtual-machines/windows/performance-diagnostics.md",
  "redirect_url": "/azure/azure-monitor/vm/performance-diagnostics?tabs=windows",

Exchange/ExchangeServer/administration/exchange-2013-end-of-support.md

@@ -0,0 +1,119 @@
+---
+title: Exchange Server 2019 and 2016 End of Support Roadmap
+description: A planning roadmap to prepare for upgrading to Exchange Online or a later version of Exchange Server.
+author: cloud-writer
+ms.author: meerak
+manager: dcscontentpm
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+ - Exchange Server
+ - CSSTroubleshoot
+ - sap:migration
+appliesto:
+ - Exchange Server 2016
+ - Exchange Server 2019
+ - Exchange Server Subscription Edition
+ - Microsoft 365 Enterprise
+ - Office 365 Enterprise
+ms.reviewer: ninob, johage, v-kccross
+search.appverid: MET150
+ms.date: 10/21/2025
+---
+
+# Exchange Server 2019 and 2016 end of support roadmap
+
+Support for Exchange Server 2019 and 2016 ended on **October 14, 2025**. If you haven't already migrated from Exchange Server 2019 or 2016 to Microsoft 365, Office 365, or Exchange Server Subscription Edition (SE), now's the time to start planning.
+
+## What does end of support mean?
+
+Most Microsoft products have a support lifecycle during which they receive new features, bug fixes, security fixes, and so on. This lifecycle lasts for 7-10 years from the product's initial release.
+
+The end of this lifecycle is known as the product's *end of support*. Because support for Exchange Server 2019 and 2016 ended on October 14, 2025, Microsoft no longer provides the following support for those products:
+
+- Technical support for problems that might occur
+- Bug fixes for issues that might affect the stability and usability of the server
+- Security fixes for vulnerabilities that might make the server vulnerable to security breaches
+- Time zone updates
+
+Although your installation of Exchange Server 2019 or 2016 continues to run, we strongly recommend that you migrate from those versions as soon as possible.
+
+## What are my options?
+
+Upgrade your on-premises servers from Exchange Server 2019 or 2016 to Exchange Server SE. You have the following options:
+
+- Migrate to Microsoft 365. Migrate mailboxes, public folders, and other data by using cutover, minimal hybrid, or full hybrid migration. Then, remove on-premises Exchange servers and Active Directory. For more information, see [How and when to decommission your on-premises Exchange servers in a hybrid deployment](/exchange/decommission-on-premises-exchange).
+
+- Upgrade to a newer version of Exchange Server without transferring the source of authority to Microsoft 365. For more information, see [Manage recipients in Exchange Hybrid environments using Management tools](/exchange/manage-hybrid-exchange-recipients-with-management-tools).
+
+> [!IMPORTANT]
+> If your organization chooses to migrate mailboxes to Microsoft 365 but plans to keep using Microsoft Entra Connect to manage user accounts in Active Directory, you have to keep at least one Exchange server. If you remove all Exchange servers, you can't make changes to Exchange recipients in Exchange Online because the source of authority is your on-premises Active Directory. In this scenario, you have the following options:
+>
+> - (Recommended) Migrate your mailboxes to Microsoft 365 and upgrade your environment to Exchange Server SE. Use Exchange Server 2019 or 2016 to connect to Microsoft 365 and migrate the mailboxes. Next, upgrade from Exchange Server 2019 or 2016 to Exchange Server SE. Then, decommission servers that run Exchange Server 2019 or 2016.
+>
+> - Upgrade from Exchange Server 2019 or 2016 to Exchange Server SE. Then, use Exchange Server SE to migrate mailboxes to Microsoft 365.
+
+The following sections discuss upgrade paths from Exchange Server 2019 or 2016.
+
+## What are the advantages of migrating to Microsoft 365?
+
+Migrating to Microsoft 365 is the best and simplest option to help you retire your Exchange Server 2019 or 2016 deployment. When you migrate to Microsoft 365, you make a single hop away from old technology, and benefit from new features, such as these:
+
+- Larger mailboxes that have greater data resilience
+- Security capabilities, such as anti-spam and anti-malware protection
+- Compliance capabilities, such as Data Loss Prevention, Retention Policies, In-Place and Litigation Hold, In-Place eDiscovery, and so on
+- Integration with SharePoint, OneDrive, Teams, Power BI, and other Microsoft 365 services
+- Focused Inbox
+- Advanced analytics and Viva Insights
+
+Microsoft 365 also gets new features and experiences first, so your organization can start to use them right away. Also, you don't have to worry about any of the following items:
+
+- Purchasing and maintaining hardware
+- Paying to run and cool your servers
+- Keeping servers up to date on security, product, and time-zone fixes
+- Maintaining server storage and software to support compliance requirements
+- Upgrading to a new version of Exchange, because you're always on the latest version with Microsoft 365
+
+### How should I migrate to Microsoft 365?
+
+Depending on your organization, you have a few options to get to Microsoft 365. You should consider a the following factors:
+
+- The number of mailboxes that you want to move
+- How long you want the migration to last
+- Whether you want a seamless integration between your on-premises environment and Microsoft 365 during the migration
+
+For guidance to choose the appropriate migration path for your organization, see [Decide on a migration path](https://support.office.com/article/Decide-on-a-migration-path-0d4f2396-9cef-43b8-9bd6-306d01df1e27).
+
+## Why should I upgrade to a newer version of Exchange Server?
+
+We strongly believe that you get the best value and user experience by migrating fully to Microsoft 365. But we understand that some organizations have to keep some on-premises Exchange servers. You might have to maintain an on-premises environment for the following reasons:
+
+- Regulatory requirements
+- To guarantee that data isn't stored in a foreign datacenter
+- Because you have unique settings or requirements that can't be met in the cloud
+- Because you need Exchange Server to manage cloud mailboxes while you still use Active Directory on-premises
+
+If you keep Exchange Server on-premises, you should upgrade your Exchange Server 2019 or 2016 deployment.
+
+For the best experience, we recommend that you upgrade your remaining on-premises environment to Exchange Server SE.
+
+- Your Exchange 2019 servers can be directly upgraded to Exchange SE "in place." Exchange SE is a cumulative upgrade to Exchange 2019. See the following Exchange Team Blog article: [Why "in-place upgrade" from Exchange 2019 to Exchange SE is low risk](https://techcommunity.microsoft.com/blog/exchange/why-%E2%80%9Cin-place-upgrade%E2%80%9D-from-exchange-2019-to-exchange-se-is-low-risk/4410173).
+- Before Exchange SE CU2 releases, you can join an Exchange SE server to your Exchange 2016 servers or mixed 2019 and 2016 organization, and then upgrade or migrate in that manner.
+
+The following Exchange Team Blog article discusses the exact migration paths for your on-premises servers to Exchange SE: [Upgrading your organization from current versions to Exchange Server SE](https://techcommunity.microsoft.com/blog/exchange/upgrading-your-organization-from-current-versions-to-exchange-server-se/4241305).
+
+## What if I need help?
+
+If you're migrating to Microsoft 365, you might be eligible to use our Microsoft FastTrack service. FastTrack provides best practices, tools, and resources to make your migration to Microsoft 365 as seamless as possible. Best of all, a support engineer walks you through from planning and design to migrating your last mailbox. For more information about FastTrack, see [Microsoft FastTrack](https://fasttrack.microsoft.com/).
+
+If you don't use FastTrack, or you're migrating to a newer version of Exchange Server, here are some resources to help you resolve any issues that you might encounter during your migration to Microsoft 365:
+
+[Technical community](https://social.technet.microsoft.com/Forums/office/home?category=exchangeserver)
+
+[Customer support for small businesses](https://support.microsoft.com/gp/support-options-for-business)
+
+## References
+
+- [Exchange Deployment Assistant](/exchange/exchange-deployment-assistant)
+- [Active Directory schema changes for Exchange Server SE](/exchange/plan-and-deploy/active-directory/ad-schema-changes)
+- [System requirements for Exchange Server SE](/exchange/plan-and-deploy/system-requirements)

Exchange/ExchangeServer/administration/exchange-2019-2016-end-of-support.md

@@ -55,7 +55,7 @@ New-SettingOverride -Name "MdbReplication" -Component WorkloadManagement -Sectio
 New-SettingOverride -Name "CiAgeOfLastNotification" -Component WorkloadManagement -Section CiAgeOfLastNotification -Parameters @("MaxConcurrency=$limit") -Reason "Allow more simultaneous mailbox moves"
 New-SettingOverride -Name "MdbAvailability" -Component WorkloadManagement -Section MdbAvailability -Parameters @("MaxConcurrency=$limit") -Reason "Allow more simultaneous mailbox moves"
 New-SettingOverride -Name "DiskLatency" -Component WorkloadManagement -Section DiskLatency -Parameters @("MaxConcurrency=$limit") -Reason "Allow more simultaneous mailbox moves"
-New-SettingOverride -Name "MdbDiskLatency" -Component WorkloadManagement -Section MdbDiskLatency -Parameters @("MaxConcurrency=$limit") -Reason "Allow more simultaneous mailbox moves"
+New-SettingOverride -Name "MdbDiskLatency" -Component WorkloadManagement -Section MdbDiskWriteLatency -Parameters @("MaxConcurrency=$limit") -Reason "Allow more simultaneous mailbox moves"
 ```
 
 To further update the WLM limit, run the following commands (this example sets the WLM limit to 35):

Exchange/ExchangeServer/migration/mailboxes-stalled-during-migration.md

@@ -102,8 +102,8 @@ items:
  href: ../administration/insufficient-access-rights-perform-operation.md
  - name: EWS App pool crashes
  href: ../administration/ews-app-pool-crashes.md
- - name: Exchange 2013 end of support roadmap
- href: ../administration/exchange-2013-end-of-support.md
+ - name: Exchange Server 2019 and 2016 end of support roadmap
+ href: ../administration/exchange-2019-2016-end-of-support.md
  - name: Exchange CU installation fails
  href: ../administration/cannot-install-exchange-cu-localized-windows.md
  - name: Fail to add mailbox database copy

Exchange/ExchangeServer/servertoc/toc.yml

@@ -5,7 +5,8 @@ summary: This library of articles provides guidance to troubleshoot and fix erro
 metadata:
  title: OneDrive for Business troubleshooting
  description: Documentation for troubleshooting common issues with OneDrive for Business.
- ms.service: one-drive
+ ms.service: microsoft-graph
+ ms.subservice: onedrive
  ms.topic: landing-page
  author: Cloud-Writer
  ms.author: meerak

SharePoint/OneDrive/onedrive-welcome.yml

@@ -24,9 +24,10 @@ ms.date: 05/08/2025
 
 As a Global or SharePoint admin, you receive an email message that contains one of the following messages:
 
-> SharePoint Online is out of storage space.
+> SharePoint Online is out of storage space. Sites are in read-only mode and changes can't be saved. 
 > 
 > There is not enough storage space on SharePoint Online.
+> Your storage is full. You can buy more storage or use Microsoft 365 Archive to free up storage space without deleting any data.
 
 ## Cause
 

SharePoint/SharePointOnline/administration/out-of-storage.md

@@ -1,7 +1,7 @@
 ---
 title: Site is protected by Microsoft 365 Backup and can't be deleted
 manager: dcscontentpm
-ms.date: 07/31/2024
+ms.date: 10/23/2025
 audience: Admin
 ms.topic: troubleshooting
 search.appverid: 
@@ -10,13 +10,14 @@ search.appverid:
 appliesto: 
  - Microsoft 365 Backup
  - SharePoint Online
- - OneDrive for Business
+ - OneDrive
 ms.custom: 
  - sap:Microsoft 365 Backup\ODSP
  - CI 193688
+ - CI 7897
  - CSSTroubleshoot
 ms.reviewer: salarson
-description: Describes an error that occurs when you try to delete a SharePoint or OneDrive for Business site that's protected by Microsoft 365 Backup. Provides steps to submit a service request to Microsoft.
+description: Provides a resolution for an error that occurs when you try to delete a SharePoint or OneDrive site that's protected by Microsoft 365 Backup.
 ---
 
 # "Site is protected by Microsoft 365 Backup and cannot be deleted" error
@@ -29,20 +30,8 @@ You try to permanently delete a site from the [SharePoint admin center](https://
 
 ## Cause  
 
-This error occurs because the site is actively protected or was protected in the past 365 days by [Microsoft 365 Backup](/microsoft-365/backup/?view=o365-worldwide&preserve-view=true). To be able to delete a site, the site backup has to be deleted. However, Microsoft 365 Backup can't delete the backups of specific SharePoint or OneDrive for Business sites. This behavior is designed to prevent malicious actors from deleting backups that are intended to quickly restore data if it's compromised.
+This error occurs because the site is actively protected or was protected in the past 365 days by [Microsoft 365 Backup](/microsoft-365/backup/?view=o365-worldwide&preserve-view=true). To be able to delete a site, the site backup has to be deleted. However, Microsoft 365 Backup can't delete the backups of specific SharePoint or OneDrive sites. This behavior is designed to prevent malicious actors from deleting backups that are intended to quickly restore data if it's compromised.
 
 ## Resolution  
 
-To delete the backup of the site that you want to delete, use the following steps to submit a support request to Microsoft:
-
-1. Sign in to the Microsoft 365 admin center by using your administrator credentials.
-1. Navigate to the following URL: 
-
- [https://aka.ms/ProtectedSiteDeletion](https://aka.ms/ProtectedSiteDeletion)
-
- This link populates the "Microsoft 365 Backup Protected Site" query in the Microsoft 365 admin center.
-1. Select **Contact support**, and then select a contact method.
-1. Leave the prepopulated **Title** field as is and the **Description** field blank.
-1. Fill in the other required fields, and then select **Contact me**.
-
-When Microsoft Support contacts you about the service request, provide the site URL and other relevant information. After the site's backup is deleted, you can delete the site.
+To delete backups of specific SharePoint sites, mailboxes, or OneDrive sites, use the steps listed in [Offboarding specific sites, mailboxes, or users](/microsoft-365/backup/backup-offboarding#offboarding-specific-sites-mailboxes-or-users&preserve-view=true).

SharePoint/SharePointOnline/sites/cannot-delete-sites-protected-by-microsoft365-backup.md

@@ -140,11 +140,14 @@
  "ms.service": {
  "SharePointHybrid/**/*.md": "sharepoint-online",
  "SharePointOnline/**/*.md": "sharepoint-online",
- "OneDrive/**/*.md": "one-drive",
+ "OneDrive/**/*.md": "microsoft-graph",
  "SharePointServer/**/*.md": "sharepoint-server-itpro",
  "SharePointExperts/**/*.md": "sharepoint-server-itpro",
  "SharePointOnline/migration/**/*.md": "microsoft-365-migration"
  },
+ "ms.subservice": {
+ "OneDrive/**/*.md": "onedrive"
+ },
  "author": {
  "**/*.md": "Cloud-Writer"
  },