Merge pull request #9075 from MicrosoftDocs/main

Auto push to live 2025-06-06 02:32:57

Author: Deland-Han

support/azure/azure-kubernetes/extensions/cannot-pull-image-from-acr-to-aks-cluster.md

@@ -1,10 +1,10 @@
 ---
 title: Can't pull images from Azure Container Registry to Kubernetes
 description: This article helps you troubleshoot the most common errors that you may encounter when pulling images from a container registry to an AKS cluster.
-ms.date: 03/25/2025
+ms.date: 06/05/2025
 author: genlin
 ms.author: genli
-ms.reviewer: chiragpa, andbar, v-weizhu, v-leedennis
+ms.reviewer: chiragpa, andbar, albarqaw, v-weizhu, v-leedennis
 ms.service: azure-kubernetes-service
 ms.custom: sap:Extensions, Policies and Add-Ons, devx-track-azurecli
 ---
@@ -349,6 +349,40 @@ spec:
   nodeSelector:
     "kubernetes.io/os": linux
 ```
+## Cause 6: Kubelet exceeds the default image pull rate limit
+
+When multiple jobs pull the same images, the Kubelet default pull rate limit might be exceeded. In this case, an error message like the following one is displayed:
+
+> Failed to pull image "acrname.azurecr.io/repo/nginx:latest": **pull QPS exceeded**. This occurred for pod \<podname\> at 4/22/2025, 12:48:32.000 PM UTC.
+
+For more information about the limit, see the [registryPullQPS configuration](https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration).
+
+### Solution: Change the value of imagePullPolicy to IfNotPresent
+
+To resolve this issue, change the value of [imagePullPolicy](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy) from `Always` to `IfNotPresent` in the deployment YAML file to prevent unnecessary pulls. `IfNotPresent` ensures that the image is pulled from the registry only if it's not already present on the node.
+
+Here's an example of the deployment YAML file:
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: my-deployment
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: my-app
+  template:
+    metadata:
+      labels:
+        app: my-app
+    spec:
+      containers:
+      - name: my-container
+        image: myacr.azurecr.io/my-image:latest
+        imagePullPolicy: IfNotPresent
+```
 
 ## More information
 

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-managed-identities.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure File Sync managed identity issues
 description: Troubleshoot common issues when your Azure File Sync deployment is configured to use managed identities.
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 04/02/2025
+ms.date: 06/05/2025
 author: khdownie
 ms.author: kendownie
 ---
@@ -65,6 +65,28 @@ When you try to delete a Storage Sync Service, you might get the following error
 
 This issue occurs when your file share has unused Azure File Sync snapshots. To reduce your cost, the unused snapshots are deleted before removing the Storage Sync Service. The snapshot count varies with the dataset size. If you can't delete the Storage Sync Service after a few hours, try again the next day.
 
+## Error "Failed to perform resource identity operation" when creating Storage Sync Service
+
+When creating a Storage Sync Service, you might get the following error: "Failed to perform resource identity operation." This error occurs when you delete a Storage Sync Service and then attempt to recreate it using the same name within the same tenant.
+
+To resolve this issue, you can create a new name for the Storage Sync Service, investigate the conflicting app in Microsoft Entra ID (and delete it manually if needed), or wait for the system to auto-clean up the app.
+
+- **Use a different Storage Sync Service name**  
+  Create the Storage Sync Service with a different name than the one previously used.
+
+- **How to investigate the conflicting service principal in Microsoft Entra ID**  
+ A conflicting service principal app might still exist in Microsoft Entra ID (formerly Azure AD). This app was likely created during the initial provisioning of the Storage Sync Service.
+
+- **Choose manual deletion (optional)**  
+  If you need immediate resolution, you can manually delete the conflicting app:  
+  1. Go to the Microsoft Entra admin center.  
+  1. Navigate to **Enterprise applications**.  
+  1. Search for the app name that matches the Storage Sync Service.  
+  1. Select the app and then select **Delete**.
+
+- **Wait for automatic cleanup**  
+  If the app was created by the Storage Sync Service provisioning process, the system will automatically delete it within 24 hours. If the service isn't urgently needed, you may choose to wait for this automatic cleanup to complete.
+
 ## Permissions required to access a storage account and Azure file share
 
 When Azure File Sync is configured to use a managed identity, your cloud and server endpoints need the following permissions to access a storage account and Azure file share:

support/power-platform/dataverse/email-exchange-synchronization/error-code-8005e274.md

@@ -1,7 +1,7 @@
 ---
 title: Error code 8005E274 when you test and enable a mailbox
 description: Provides a resolution for error code 8005E274 that occurs when you test and enable a mailbox for server-side synchronization.
-ms.date: 04/29/2024
+ms.date: 06/06/2025
 ms.custom: sap:Email and Exchange Synchronization\Set up and configuration of server-side synchronization
 author: rahulmital
 ms.author: rahulmital
@@ -14,9 +14,13 @@ This article provides a resolution for error code 8005E274 that occurs when you
 
 When a user tries to [test and enable a mailbox](/power-platform/admin/connect-exchange-online#test-the-configuration-of-mailboxes) in Microsoft Dataverse, the test fails with error code 8005E274.
 
+You might also see the following error message in the [Alerts](/power-platform/admin/monitor-email-processing-errors#view-alerts) section of the mailbox record:
+
+> **Email Server Error Code:** MailboxNotEnabledForRESTAPI
+
 ## Cause
 
-This issue occurs because the associated Exchange mailbox isn't enabled for the REST API. The mailbox associated with the email address isn't enabled for the REST API connectivity in the Microsoft 365 tenant associated with an email server profile. This issue can occur if the mailbox doesn't have an Exchange Online license, is disabled, or exists in an Exchange on-premises hybrid deployment.
+This issue occurs because the Exchange mailbox associated with the email address isn't enabled for REST API connectivity in the Microsoft 365 tenant relative to the configured email server profile. This issue can occur if the mailbox doesn't have an Exchange Online license, is disabled, or exists in an Exchange on-premises hybrid deployment.
 
 ## Resolution