Merge pull request #7972 from MicrosoftDocs/main

Auto push to live 2025-01-02 18:00:02

Author: Deland-Han

support/sales-copilot/crm-permissions-and-configurations/fix-mailbox-errors-in-dynamics-365.md

@@ -1,7 +1,7 @@
 ---
 title: Fix mailbox errors in Dynamics 365
 description: Resolves an error that might occur when you try to save an email or a meeting to Dynamics 365 using the Microsoft Copilot for Sales for Outlook add-in.
-ms.date: 01/10/2024
+ms.date: 01/03/2025
 author: sbmjais
 ms.author: shjais
 manager: shujoshi
@@ -11,9 +11,6 @@ ms.custom: sap:CRM Permissions and Configurations\CRM Settings
 
 This article helps you troubleshoot and resolve the "Fix mailbox errors in Dynamics 365" error when you use Microsoft Copilot for Sales in Outlook.
 
-> [!NOTE]
-> Microsoft Sales Copilot is rebranded as Microsoft Copilot for Sales in January 2024. The screenshots in this article will be updated with the new name soon.
-
 ## Who is affected?
 
 | Requirement type |Description  |
@@ -46,7 +43,7 @@ To resolve the error, you must locate the specific error as part of the mailbox
 1. Open the CRM instance you connected to Copilot for Sales.
 
     > [!NOTE]
-    > To get the CRM instance URL, select **Options** (**…**) in the upper-right corner of the Copilot for Sales pane. The URL is displayed under **Signed in to Dynamics 365**.
+    > To get the CRM instance URL, go to the [Home tab](/microsoft-sales-copilot/personal-app#home-tab) in the Copilot for Sales personal app in [Outlook](/microsoft-sales-copilot/personal-app#open-the-personal-app-in-outlook) or [Teams](/microsoft-sales-copilot/personal-app#open-the-personal-app-in-teams), and select the environment name in the upper-right corner.
 
 2. Select **Settings** > **Personalization Settings**.
 

support/windows-client/user-profiles-and-logon/cached-user-logon-fails-lsasrv-event-45058.md

@@ -1,7 +1,7 @@
 ---
 title: Cached user logon fails with LSASRV event 45058
-description: Fixes an issue that occurs when logging on to a domain-joined Windows Vista or Windows 7 computer using cached credentials.
-ms.date: 12/26/2023
+description: Fixes an issue that occurs when logging on to a domain-joined Windows computer using cached credentials.
+ms.date: 01/02/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -10,16 +10,16 @@ ms.custom: sap:User Logon and Profiles\Service Account and Interactive User Logo
 ---
 # Cached user logon fails when LSASRV event 45058 indicates FIFO deletion of cached credential
 
-This article fixes a logon failure that occurs when logging on to a domain-joined Windows Vista or Windows 7 computer using cached credentials.
+This article fixes a logon failure that occurs when logging on to a domain-joined Windows computer using cached credentials.
 
-_Applies to:_   Windows 7 Service Pack 1  
+_Applies to:_   Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025  
 _Original KB number:_   2555663
 
 ## Symptoms
 
-1. Users receive the following error when logging on to a domain-joined Windows Vista or Windows 7 computer using cached credentials:
+1. Users receive the following error when logging on to a domain-joined Windows computer using cached credentials:
 
-    > There are currently no logon servers available to service the logon request.
+   > There are currently no logon servers available to service the logon request.
 
 2. LsaSrv Event 45058, logged in the System event log of a domain-joined workstation, indicates that the operating system has deleted the cached credential for the user specified in the event:
 
@@ -39,7 +39,7 @@ _Original KB number:_   2555663
 
 The user logon error occurs when a user's cached credentials have been purged from the local computer by more recent domain user logons.
 
-Windows Vista and Windows 7 operating systems cache credentials for a finite number of user accounts (assuming cached credentials haven't been disabled).
+Windows operating systems cache credentials for a finite number of user accounts (assuming cached credentials haven't been disabled).
 
 Once the cached logon quota has been reached, the operating system will purge the oldest cached credential from the local computer so that the credentials for the next unique domain user successfully authenticated by a domain controller may be cached. The logging of the LsaSrv 45058 event indicates that the cached logon quota has been reached, triggering the deletion of the oldest user credential cached on the local machine.
 
@@ -72,6 +72,6 @@ Cached credentials can also be managed with group policy by configuring:
 
 Group Policy Setting path: Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options.
 
-Group Policy Setting: Interactive logon: Number of previous logons to cache (in case domain controller is not available)
+[Group Policy Setting: Interactive logon: Number of previous logons to cache (in case domain controller is not available)](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available)
 
 The workstation the user needs access to must have physical connectivity with the domain and the user must authenticate with a domain controller to cache their credentials again.