Merge pull request #2043 from microsoft/bilong-emerging

Fix the number of columns on the blank line

docs/Emerging-Issues.md

@@ -22,7 +22,7 @@ This page lists emerging issues for Exchange On-Premises deployments, possible r
 | 3/14/2023 | [February 2023 Security Update](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-february-2023-exchange-server-security-updates/ba-p/3741058) for Exchange 2016, Exchange 2019, Exchange 2013 | After installing February 2023 security update, customers are seeing EWS application pool crash with Event ID 4999 with following error <BR><BR> E12IIS, c-RTL-AMD64, 15.01.2507.021, w3wp#MSExchangeServicesAppPool, M.Exchange.Diagnostics, M.E.D.ChainedSerializationBinder.EnforceBlockReason, M.E.Diagnostics.BlockedDeserializeTypeException, 437c-dumptidset, 15.01.2507.021. <BR><BR> The issue is causing connectivity issues to EWS based clients (Outlook for Mac) | **Update on 3/14/2023** <BR> The issue is fixed in [March 2023 security update for Exchange servers](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2023-exchange-server-security-updates/ba-p/3764224) <BR> Please follow the steps in [this KB](https://support.microsoft.com/help/5024257) |
 | 3/14/2023 | [February 2023 Security Update](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-february-2023-exchange-server-security-updates/ba-p/3741058) for Exchange 2016, Exchange 2019, Exchange 2013 | Some customers are reporting issues with Outlook/OWA add-ins, like add-in not listing in EAC or with the Get-App command. Additionally, they may notice EWS application pool crash with Event ID 4999 in the application log of the Exchange server. | **Update on 3/14/2023** <BR> The issue is fixed in [March 2023 security update for Exchange servers](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2023-exchange-server-security-updates/ba-p/3764224) |
 | 3/14/2023 | [January 2023 Security Update](https://www.microsoft.com/en-us/download/details.aspx?id=104914) for Exchange 2016, Exchange 2019 |The Exchange toolbox may start crashing on launch after [certificate Serialization for PowerShell](https://aka.ms/HC-SerializedDataSigning) is enabled. The error noticed is "Deserialization fails: System.Reflection.TargetInvocationException". <BR><BR> The issue happens only on Exchange 2016 and Exchange 2019|  **Update on 3/14/2023** <BR> The issue is fixed in [March 2023 security update for Exchange servers](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2023-exchange-server-security-updates/ba-p/3764224) |
-|-|-|-|-|-|-|
+|-|-|-|-|
 | 1/24/2023 | [January 2023 Security Update](https://www.microsoft.com/en-us/download/details.aspx?id=104914) for Exchange 2016, Exchange 2019 | After installing January 2023 security update and enabling [certificate signing for serialization of PowerShell](https://aka.ms/HC-SerializedDataSigning), you may find  various Exchange commands and scripts (example: RedistributeActiveDatabases.ps1) that use deserialization failing with the error similar to : <BR> Error: "Cannot convert the value of type.....to type" | Use [this script](https://aka.ms/MonitorExchangeAuthCertificate) to update the auth certificate |
 | 1/24/2023 | [January 2023 Security Update](https://www.microsoft.com/en-us/download/details.aspx?id=104914) for Exchange 2016, Exchange 2019 | RecoverServer will fail at pre-requisites check with following error: <BR> "Exchange Server version Version 15.1 (Build 2507.17) or later must be used to perform a recovery of this server." | **Update on 02/23/2023** <BR>The issue has been fixed in [February 2023 Security Update for Exchange servers](https://support.microsoft.com/KB/5023038), however, the following workaround still needs to be used for servers that are on January 2023 Security Update <BR><BR> **Workaround** <BR> Use the steps in [this](https://learn.microsoft.com/exchange/troubleshoot/setup/version-error-in-recover-server-mode-install) article |
 | 1/24/2023 | [January 2023 Security Update](https://www.microsoft.com/en-us/download/details.aspx?id=104914) for Exchange 2016 installed on Windows 2012 R2, other versions are not affected |The Exchange services in Automatic start-up mode will not start after reboot of the server. The services start successfully if started manually| **Update on 02/23/2023**<BR>The issue has been fixed in [February 2023 Security Update for Exchange servers](https://support.microsoft.com/KB/5023038) |