Merge pull request #7988 from ErikjeMS/win365

39845820 add issue

Author: PRMerger4

windows-365/enterprise/known-issues-enterprise.md

@@ -38,6 +38,18 @@ The following items are known issues for Windows 365 Enterprise.
 
 A [resize](resize-cloud-pc.md) of a Cloud PC eliminates all existing [restore](restore-overview.md) points for that Cloud PC. New restore points will be captured at the intervals defined in the user setting.
 
+## Outlook only downloads one month of mail<!--39845820-->
+
+Outlook only downloads one month of previous mail and this can't be changed in Outlook settings.
+
+ **Troubleshooting steps**:
+
+1. Launch registry editor.
+2. Remove the **syncwindowsetting** regkey under the path \HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\office\16.0\outlook\cached mode.
+3. Add the **syncwindowsetting** regkey with the value 1 under the path HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Cached Mode.
+
+After completing these steps, the default will be one month. However, the download period can be changed in Outlook settings.
+
 ## Windows doesn’t scan for software updates until the first time a user signs in<!--38212344-->
 
 While a Windows PC (physical or Cloud PC) sits idle before the first user signs in, Windows Update doesn’t scan for or install monthly quality patches. This means that the PC might miss important security updates. Without the latest security updates, the device is exposed to security vulnerabilities.
@@ -48,7 +60,7 @@ While a Windows PC (physical or Cloud PC) sits idle before the first user signs
 
 Upgrading an existing Cloud PC from Windows 10 to Windows 11 using the Settings app may fail.
 
-## Troubleshooting steps
+**Troubleshooting steps**:
 
 1. Edit the related provisioning policy to change the gallery image to Windows 11.
 2. Reprovision the Cloud PC.
@@ -60,7 +72,7 @@ Windows 365 provisioning failures may occur because both:
 - the Desired State Configuration (DSC) extension isn't signed and
 - the PowerShell Execution policy is set to Allsigned in the Group Policy Object (GPO)
 
-**Troubleshooting steps**: 
+**Troubleshooting steps**:
 
 1. Did the Azure network connection (ANC) fail with the following error: `"An internal error occurred. The virtual machine deployment timed out."`?
 2. If yes, review the related GPO. Is PowerShell Execution set to AllSigned?
@@ -87,7 +99,7 @@ The following device compliance settings may report as **Not Compliant** when be
 
 1. [Create a filter for all Cloud PCs](create-filter.md#create-a-filter-for-all-cloud-pcs).
 2. For any existing device compliance policies that both evaluate to a Cloud PC and contain either of the **Not Compliant** settings, use this new filter to exclude Cloud PCs from the policy assignment.
-3. Create a new device compliance policy without either of the **Not Compliant** settings and use this new filter to include Cloud PCs for the policy assignment. 
+3. Create a new device compliance policy without either of the **Not Compliant** settings and use this new filter to include Cloud PCs for the policy assignment.
 
 ## Next steps