Merge pull request #8668 from MicrosoftDocs/main

Deland-Han · web-flow · commit b35b1914285c · 2025-04-09T10:22:14.000+08:00
Auto push to live 2025-04-08 10:00:02
diff --git a/support/azure/azure-kubernetes/create-upgrade-delete/error-code-operationnotallowed-publicipcountlimitreached.md b/support/azure/azure-kubernetes/create-upgrade-delete/error-code-operationnotallowed-publicipcountlimitreached.md
@@ -1,9 +1,9 @@
 ---
 title: Troubleshoot OperationNotAllowed or PublicIPCountLimitReached
 description: Learn how to troubleshoot the OperationNotAllowed or PublicIPCountLimitReached quota error when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 10/28/2024
+ms.date: 04/03/2024
 editor: v-jsitser
-ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, dorinalecu
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the OperationNotAllowed or PublicIPCountLimitReached quota error code so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
diff --git a/support/azure/azure-kubernetes/create-upgrade-delete/error-code-toomanyrequestsreceived-subscriptionrequeststhrottled.md b/support/azure/azure-kubernetes/create-upgrade-delete/error-code-toomanyrequestsreceived-subscriptionrequeststhrottled.md
@@ -1,9 +1,9 @@
 ---
 title: Troubleshoot the TooManyRequestsReceived or SubscriptionRequestsThrottled error code
 description: Learn how to troubleshoot the TooManyRequestsReceived or SubscriptionRequestsThrottled error when you try to delete an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/18/2024
+ms.date: 04/03/2025
 editor: v-jsitser
-ms.reviewer: rissing, chiragpa, edneto, v-leedennis
+ms.reviewer: rissing, chiragpa, edneto, v-leedennis, dorinalecu
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the TooManyRequestsReceived or SubscriptionRequestsThrottled error code so that I can successfully delete an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
diff --git a/support/power-platform/dataverse/welcome-dataverse.yml b/support/power-platform/dataverse/welcome-dataverse.yml
@@ -9,18 +9,27 @@ metadata:
   ms.topic: landing-page # Required
   author: rahulmital #Required; your GitHub user alias, with correct capitalization.
   ms.author: rahulmital #Required; microsoft alias of author; optional team alias.
-  ms.date: 04/22/2024
+  ms.date: 04/09/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
 landingContent:
+
 # Card
-- title: Bulk deleting data
+- title: Dynamics 365 App for Outlook
   linkLists:
     - linkListType: how-to-guide
-      links:
-        - text: Bulk operation errors
-          url: bulk-deleting-data/bulk-operation-errors.md
+      links:        
+        - text: App for Outlook authentication pop-up is blank and unable to sign in
+          url: d365-app-outlook/dynamics-app-for-outlook-authentication-pop-up-blank-cannot-proceed.md
+        - text: Dynamics 365 App for Outlook doesn't appear within Outlook
+          url: d365-app-outlook/app-does-not-appear-within-outlook.md
+        - text: '"Something went wrong during sign-in" error when accessing'
+          url: d365-app-outlook/app-does-not-appear-within-outlook.md
+        - text: '"Track and Set Regarding are currently disabled" error'
+          url: d365-app-outlook/something-went-wrong-during-sign.md
+        - text: You don't have required privilege (prvReadOrganization) error
+          url: d365-app-outlook/dynamics-app-for-outlook-authentication-pop-up-blank-cannot-proceed.md
 
 # Card
 - title: Dataverse Web API and SDK
@@ -33,12 +42,32 @@ landingContent:
           url: dataverse-web-api-and-sdk/web-api-client-errors.md
 
 # Card
-- title: Plug-in execution
+- title: Email and Exchange Synchronization
   linkLists:
     - linkListType: how-to-guide
       links:
-        - text: Dataverse plug-ins
-          url: plug-in-execution/dataverse-plug-ins-errors.md
+        - text: A Tracked to Dynamics 365 category is added to a user's mailbox
+          url: email-exchange-synchronization/tracked-to-dynamics-365-category-added.md
+        - text: 401 Unauthorized exception when using server-side synchronization
+          url: email-exchange-synchronization/exception-when-using-server-side-sync.md
+        - text: '"You are not part/member of organization; Account disabled; no instances found; Invalid User Authorization error"'
+          url: email-exchange-synchronization/error-when-signing-dynamics-365.md
+        - text: '"The account does not have permission to impersonate the requested user" error when selecting Test Connection'
+          url: email-exchange-synchronization/the-account-does-not-have-permission-to-impersonate-the-requested-user-error.md
+        - text: Troubleshoot and monitor server-side synchronization
+          url: email-exchange-synchronization/troubleshooting-monitoring-server-side-synchronization.md
+        - text: '"You cannot send email as the selected user" error when sending an email as another user'
+          url: email-exchange-synchronization/cannot-send-email-as-another-user.md
+
+# Card
+- title: Environment and app access
+  linkLists:
+    - linkListType: how-to-guide
+      links:
+        - text: Troubleshoot user access issues for different environments
+          url: environment-app-access/troubleshooting-user-needs-read-write-access-organization.md
+        - text: Troubleshoot missing environments
+          url: environment-app-access/troubleshoot-missing-environments.md   
 
 # Card
 - title: User permissions
@@ -49,23 +78,27 @@ landingContent:
           url: user-permissions/cleanup-inherited-access.md
         - text: Dataverse client errors
           url: user-permissions/client-errors.md
+
 # Card
 - title: Working with solutions
   linkLists:
     - linkListType: how-to-guide
       links:
-        - text: '"An entitykey with the selected attributes already exists" error'
-          url: working-with-solutions/entitykey-selected-attributes-already-exists.md    
-        - text: '"Failed deleting solution" error due to circular dependencies between solutions'
-          url: working-with-solutions/circular-dependencies-between-solutions.md
-        - text: '"Full formXml is expected to create a form" error'
-          url: working-with-solutions/full-formxml-expected-to-create-form-error.md
-        - text: '"PrimaryName attribute not found for entity" error'
-          url: working-with-solutions/primaryname-attribute-not-found.md
-        - text: '"Solution cannot be deleted due to dependencies" error'
-          url: working-with-solutions/solution-cannot-be-deleted-due-to-dependencies.md
-        - text: '"You cannot delete this form because it is the only fallback form" error'
-          url: working-with-solutions/you-cannot-delete-this-form-only-fallback.md
+        - text: Concurrent solution operation failures
+          url: working-with-solutions/concurrent-solution-operation-failures.md
+        - text: Changes aren't effective after solution import
+          url: working-with-solutions/changes-not-effective-solution-import.md
+        - text: Error code 80040203 (Invalid Argument) error when importing a solution
+          url: working-with-solutions/error-code-80040203-invalid-argument-error.md
+        - text: Missing dependencies error during solution import
+          url: working-with-solutions/missing-dependency-on-solution-import.md
+        - text: Maximum row size exceeds the allowed maximum during solution import
+          url: working-with-solutions/maximum-row-size-exceeds.md
+        - text: Solution import or application installation failure due to missing privileges
+          url: working-with-solutions/install-failure-priviledge-not-assigned.md
+        - text: '"The import of solution failed" error'
+          url: working-with-solutions/the-import-of-solution-failed-error-when-importing-solution.md
+
 
 # Card
 - title: Documentation and training
diff --git a/support/sql/database-engine/availability-groups/alwayson-availability-databases-recovery-pending-suspect.md b/support/sql/database-engine/availability-groups/alwayson-availability-databases-recovery-pending-suspect.md
@@ -1,9 +1,9 @@
 ---
 title: Always On DB in recovery pending or suspect state 
 description: This article describes the errors and limitations of an availability database in Microsoft SQL Server that is in a Recovery Pending or Suspect state and how to restore the database to full functionality in an availability group.
-ms.date: 08/03/2020
+ms.date: 04/08/2025
 ms.custom: sap:Always On Availability Groups (AG)
-ms.reviewer: ramakoni, cmathews
+ms.reviewer: ramakoni, cmathews, jopilov
 ---
 
 # Troubleshoot Always On availability databases in Recovery Pending or Suspect state in SQL Server
diff --git a/support/sql/database-engine/availability-groups/troubleshoot-availability-group-database-reverting-state.md b/support/sql/database-engine/availability-groups/troubleshoot-availability-group-database-reverting-state.md
@@ -1,9 +1,9 @@
 ---
 title: Troubleshoot an availability group database in reverting state
 description: This article helps you troubleshoot an availability group database in reverting state where Not Synchronizing is reported on the primary.
-ms.date: 02/06/2024
+ms.date: 04/08/2025
 ms.custom: sap:Always On Availability Groups (AG)
-ms.reviewer: cmathews, v-sidong
+ms.reviewer: cmathews, jopilov, v-sidong
 ---
 
 # Troubleshoot an Availability Group database in reverting state
diff --git a/support/sql/database-engine/availability-groups/troubleshooting-intermittent-connection-timeouts-availability-groups.md b/support/sql/database-engine/availability-groups/troubleshooting-intermittent-connection-timeouts-availability-groups.md
@@ -1,9 +1,9 @@
 ---
 title: Troubleshooting intermittent connection time-outs between availability group replicas
 description: This article helps you diagnose intermittent connection time-outs that are reported between availability group replicas. 
-ms.date: 04/04/2023
+ms.date: 04/08/2025
 ms.custom: sap:Always On Availability Groups (AG)
-ms.reviewer: ramakoni, cmathews, v-jayaramanp
+ms.reviewer: ramakoni, cmathews, v-jayaramanp, jopilov
 ---
 
 # Troubleshooting intermittent connection time-outs between availability group replicas
diff --git a/support/sql/database-engine/availability-groups/troubleshooting-log-send-queuing-in-alwayson-availability-group.md b/support/sql/database-engine/availability-groups/troubleshooting-log-send-queuing-in-alwayson-availability-group.md
@@ -1,9 +1,9 @@
 ---
 title: Troubleshooting long send queueing in an Always On availability group
 description: This article troubleshoots problems related to log send queueing in an Always On availability group. 
-ms.date: 02/20/2023
+ms.date: 04/08/2025
 ms.custom: sap:Always On Availability Groups (AG)
-ms.reviewer: ramakoni, v-jayaramanp
+ms.reviewer: ramakoni, v-jayaramanp, jopilov
 ---
 
 # Troubleshooting log send queueing in an Always On availability group
diff --git a/support/sql/database-engine/connect/consistent-authentication-connectivity-issues.md b/support/sql/database-engine/connect/consistent-authentication-connectivity-issues.md
@@ -1,7 +1,7 @@
 ---
 title: Overview of consistent authentication issues in SQL Server
 description: This article discusses consistent authentication issues in SQL Server, related error messages, and solutions to troubleshoot various issues.
-ms.date: 05/27/2024
+ms.date: 04/08/2025
 ms.reviewer: jopilov, haiyingyu, prmadhes, v-jayaramanp
 ms.custom: sap:Connection issues
 ---
diff --git a/support/sql/database-engine/connect/resolve-connectivity-errors-checklist.md b/support/sql/database-engine/connect/resolve-connectivity-errors-checklist.md
@@ -1,10 +1,11 @@
 ---
 title: Prerequisites and checklist for resolving connectivity errors
 description: Provides prerequisites and a checklist for troubleshooting SQL Server connectivity issues.
-ms.date: 05/25/2022
+ms.date: 04/08/2025
 ms.custom: sap:Database Connectivity and Authentication
 author: HaiyingYu
 ms.author: haiyingyu
+ms.reviewer: jopilov
 ---
 # Recommended prerequisites and checklist for troubleshooting SQL Server connectivity issues
 
diff --git a/support/sql/database-engine/connect/tls-upgrade-wkflow-1-2.md b/support/sql/database-engine/connect/tls-upgrade-wkflow-1-2.md
@@ -1,7 +1,7 @@
 ---
 title: TLS 1.2 upgrade workflow
 description: This article discusses the procedure about how to upgrade SQL Server client and servers to the TLS 1.2 protocol for SQL Server.
-ms.date: 01/29/2024
+ms.date: 04/08/2025
 ms.custom: sap:Database Connectivity and Authentication
 ms.reviewer: jopilov, haiyingyu, prmadhes, v-jayaramanp
 ---
diff --git a/support/sql/database-engine/database-file-operations/support-network-database-files.md b/support/sql/database-engine/database-file-operations/support-network-database-files.md
@@ -1,9 +1,9 @@
 ---
 title: Support for network database files
 description: This article describes support for network database files in SQL Server and how to configure SQL Server to store a database on a networked server or on an NAS storage server.
-ms.date: 09/04/2023
+ms.date: 04/08/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
-ms.reviewer: SANJAYAN
+ms.reviewer: jopilov, saba
 ---
 # Description of support for network database files in SQL Server
 
diff --git a/support/sql/database-engine/failover-clusters/error-install-sql-server-windows-server-cluster.md b/support/sql/database-engine/failover-clusters/error-install-sql-server-windows-server-cluster.md
@@ -1,8 +1,9 @@
 ---
 title: Install SQL Server on Windows Server cluster
 description: Provides a workaround for the problem that occurs when you install SQL Server on Windows Server cluster.
-ms.date: 11/19/2020
+ms.date: 04/08/2025
 ms.custom: sap:Always On Failover Cluster Instance (FCI)
+ms.reviewer: jopilov
 ---
 
 # Error message when you install SQL Server on a Windows Server cluster
diff --git a/support/sql/database-engine/install/windows/error-set-up-update-instances.md b/support/sql/database-engine/install/windows/error-set-up-update-instances.md
@@ -1,9 +1,9 @@
 ---
 title: Attempted to perform an unauthorized operation error
 description: This article provides a resolution for the problem where setting up or updating SQL Server instances fails and returns an error message.
-ms.date: 01/15/2021
+ms.date: 04/08/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
-ms.reviewer:  
+ms.reviewer: jopilov
 ---
 # Attempted to perform an unauthorized operation error when you set up or update SQL Server instances
 
diff --git a/support/sql/database-engine/install/windows/sql-server-upgrade-failed-error-15151.md b/support/sql/database-engine/install/windows/sql-server-upgrade-failed-error-15151.md
@@ -1,7 +1,7 @@
 ---
 title: SQL Server upgrade fails with error 15151 when executing Update Database scripts
 description: This article describes error 15151 that stops a SQL Server upgrade when update database scripts are run.
-ms.date: 08/17/2023
+ms.date: 04/08/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
 ms.reviewer: jopilov, v-jayaramanp
 ---
diff --git a/support/sql/database-engine/install/windows/user-data-log-directory-invalid.md b/support/sql/database-engine/install/windows/user-data-log-directory-invalid.md
@@ -1,9 +1,9 @@
 ---
 title: Invalid directory error when installing SQL CU or SP
 description: This article provides resolutions for the problem that occurs when you install a Cumulative Update or a Service Pack for a SQL Server instance.
-ms.date: 07/28/2023
+ms.date: 04/08/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
-ms.reviewer: lramirez, pijocoder
+ms.reviewer: lramirez, jopilov
 ---
 
 # Error that Data or Log directory in the registry is not valid when installing SQL Server Cumulative Update or a Service Pack
diff --git a/support/sql/database-engine/performance/buffer-pool-scan-runs-slowly-large-memory-machines.md b/support/sql/database-engine/performance/buffer-pool-scan-runs-slowly-large-memory-machines.md
@@ -1,7 +1,7 @@
 ---
 title: Operations that trigger buffer pool scan may run slowly on large-memory computers
 description: This article describes how a scan of the SQL Server buffer pool might take a long time on a large-memory computer.
-ms.date: 06/20/2022
+ms.date: 04/08/2025
 ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage)
 ms.reviewer: jopilov
 ms.topic: article 
@@ -36,7 +36,7 @@ Here are some operations that may trigger a buffer pool scan to occur:
 
 Starting with [SQL Server 2016 SP3](https://support.microsoft.com/help/5003279), [SQL Server 2017 CU23](https://prod.support.services.microsoft.com/topic/kb5000685-cumulative-update-23-for-sql-server-2017-22b653c7-8487-4564-9db2-b5c1bd465145?preview=true#bkmk_13741858) and [SQL Server 2019 CU9](https://support.microsoft.com/topic/kb5000642-cumulative-update-9-for-sql-server-2019-97ad5c3e-e002-4b6d-b566-698bf70ca44a#bkmk_13744390), an error message was added to the SQL Server [Error log](/sql/tools/configuration-manager/viewing-the-sql-server-error-log) to indicate that a buffer pool scan took a long time (10 seconds or longer):
 
->Buffer Pool scan took 14 seconds: database ID 7, command 'BACKUP DATABASE', operation 'FlushCache', scanned buffers 115, total iterated buffers 204640239, wait time 0 ms. See 'https://go.microsoft.com/fwlink/?linkid=2132602' for more information.
+> Buffer Pool scan took 14 seconds: database ID 7, command 'BACKUP DATABASE', operation 'FlushCache', scanned buffers 115, total iterated buffers 204640239, wait time 0 ms. See 'https://go.microsoft.com/fwlink/?linkid=2132602' for more information.
 
 ### Extended Event to diagnose a long scan
 
@@ -49,11 +49,11 @@ If a scan takes more than 1 second, the XEvent will be recorded as follows when
 |buffer_pool_scan_complete|7|1308|BACKUP DATABASE|FlushCache|243|19932814|
 
 > [!NOTE]
-> The threshold is in the XEvent is smaller to allow you to capture information at a finer-granularity.
+> The threshold in the XEvent is smaller to allow you to capture information at a finer-granularity.
 
 ## Workaround
 
-Prior to SQL Server 2022, there was no way to eliminate this problem. It is not recommended to perform any action to clear the buffer pool as dropping clean buffers ([DBCC DROPCLEANBUFFERS](/sql/t-sql/database-console-commands/dbcc-dropcleanbuffers-transact-sql)) from the buffer pool may result in a significant performance degradation. Removing database pages from memory will cause subsequent query executions to re-read the data from the database files on disk. This process of accessing data via disk I/O causes queries to be slow. 
+Prior to SQL Server 2022, there was no way to eliminate this problem. It isn't recommended to perform any action to clear the buffer pool as dropping clean buffers ([DBCC DROPCLEANBUFFERS](/sql/t-sql/database-console-commands/dbcc-dropcleanbuffers-transact-sql)) from the buffer pool may result in a significant performance degradation. Removing database pages from memory will cause subsequent query executions to re-read the data from the database files on disk. This process of accessing data via disk I/O causes queries to be slow. 
 
 In SQL Server 2022, this problem is mitigated because buffer pool scans are parallelized by utilizing multiple cores. There will be one task per 8 million buffers (64 GB) where a serial scan will still be used if there are less than 8 million buffers. For more information, watch [Buffer Pool Parallel Scan](/shows/data-exposed/sql-server-2022-introducing-buffer-pool-parallel-scan).
 
diff --git a/support/sql/database-engine/performance/memory-optimized-tempdb-out-of-memory.md b/support/sql/database-engine/performance/memory-optimized-tempdb-out-of-memory.md
@@ -1,7 +1,7 @@
 ---
 title: Memory-optimized tempdb metadata out of memory errors
 description: This article helps you to troubleshoot out-of-memory issues with memory-optimized tempdb metadata.
-ms.date: 03/04/2024
+ms.date: 04/08/2025
 ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage)
 ms.reviewer: jopilov, hesha, randolphwest
 author: Hemin-msft
diff --git a/support/sql/releases/servicing-models-sql-server.md b/support/sql/releases/servicing-models-sql-server.md
@@ -1,8 +1,8 @@
 ---
 title: Servicing models for SQL Server
 description: This article describes the information regarding servicing channels for currently supported versions of SQL Server.
-ms.date: 02/15/2023
-ms.reviewer: ramakoni, v-sidong
+ms.date: 04/08/2025
+ms.reviewer: jopilov, ramakoni, v-sidong
 ms.topic: conceptual
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
 ---
diff --git a/support/sql/tools/sqliosim-utility-simulate-activity-disk-subsystem-linux.md b/support/sql/tools/sqliosim-utility-simulate-activity-disk-subsystem-linux.md
@@ -3,8 +3,8 @@ title: Use the SQLIOSim utility on Linux
 description: This article describes how to use SQLIOSim utility to simulate SQL Server activity on a disk subsystem on Linux.
 author: HaiyingYu
 ms.author: haiyingyu
-ms.reviewer: amitkh, dansha, rafidl, Suresh.Kandoth, randolphwest
-ms.date: 07/14/2023
+ms.reviewer: amitkh, dansha, rafidl, sureshka, randolphwest, jopilov
+ms.date: 04/08/2025
 ms.topic: how-to
 ms.custom: sap:SQL Server Management, Query and Data Tools, linux-related-content
 ---
diff --git a/support/windows/win32/japanese-handwritten-characters-not-recognized.md b/support/windows/win32/japanese-handwritten-characters-not-recognized.md
@@ -0,0 +1,28 @@
+---
+title: Japanese Handwritten Characters Aren't Recognized by Microsoft.Ink.Recognizer
+description: Describes an issue where Japanese handwritten characters aren't recognized using Microsoft.Ink.Recognizer on Windows 11 version 24H2 and Windows Server 2025.
+ms.date: 04/09/2025
+ms.reviewer: soshogoh, hirotoh, davean, v-sidong
+ms.custom: sap:Desktop app UI development\User interaction (keyboard, mouse, pen and touch)
+---
+# Japanese handwritten characters aren't recognized using Microsoft.Ink.Recognizer
+
+## Symptoms
+
+When using `Microsoft.Ink.Recognizer` as the recognition engine on Windows 11 version 24H2 and Windows Server 2025, you might encounter the following issues:
+
+- Issue 1
+
+  The Japanese handwritten characters aren't recognized correctly.
+
+  For example, when you handwrite Japanese `カスイ`, the result is `カイ`, which isn't expected.
+
+- Issue 2
+
+  When you perform character recognition with specified stroke data, the specified character range isn't correctly applied.
+
+  For example, when you handwrite `あいう`, specify the character range as `ラ リ ル レ ロ`, and then execute handwritten character recognition, the actual result is `あいう`. However, the expected result is `ロロラ`.
+
+## Status
+
+Microsoft has confirmed this is a problem in Windows 11 version 24H2 and Windows Server 2025.
diff --git a/support/windows/win32/toc.yml b/support/windows/win32/toc.yml
@@ -29,6 +29,8 @@
       href: half-width-full-width-katakana-hiragana-characters.md
     - name: IME crashes with cross-thread sent messages
       href: ime-crash-processing-cross-thread-sent-message.md
+    - name: Japanese handwritten characters aren't recognized
+      href: japanese-handwritten-characters-not-recognized.md
     - name: Navigation bar doesn't update when navigating shell namespace extension folders
       href: navigation-bar-not-update-navigating-shell-namespace-extension-folders.md
     - name: Owner window gets activated when taskbar buttons are created
