Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into yelevin/strong-identifier-examples

Author: yelevin

articles/backup/azure-kubernetes-service-backup-troubleshoot.md

@@ -129,6 +129,41 @@ This error appears due to absence of these FQDN rules because of which configura
 
 6. Delete and reinstall Backup Extension to initiate backup. 
 
+### Scenario 4
+
+**Error message**:
+
+   ```Error
+   "message": "Error: [ InnerError: [Helm installation failed : Unable to create/update Kubernetes resources for the extension : Recommendation Please check that there are no policies blocking the resource creation/update for the extension : InnerError [release azure-aks-backup failed, and has been uninstalled due to atomic being set: failed pre-install: job failed: BackoffLimitExceeded]]] occurred while doing the operation : [Create] on the config, For general troubleshooting visit: https://aka.ms/k8s-extensions-TSG, For more application specific troubleshooting visit: Facing trouble? Common errors and potential fixes are detailed in the Kubernetes Backup Troubleshooting Guide, available at https://www.aka.ms/aksclusterbackup",
+   ```
+The upgrade CRDs pre-install job is failing in the cluster.
+
+**Cause**: Pods Unable to Communicate with Kube API Server
+
+**Debug**
+
+1. Check for any events in the cluster related to pod spawn issue.
+```azurecli-interactive
+kubectl events -n dataprotection-microsoft
+```
+2. Check the pods for dataprotection crds.
+```azurecli-interactive
+kubectl get pods -A | grep "dataprotection-microsoft-kubernetes-agent-upgrade-crds"
+```
+3. Check the pods logs.
+```azurecli-interactive
+kubectl logs -f --all-containers=true --timestamps=true -n dataprotection-microsoft <pod-name-from-prev-command>
+```
+Example log message:
+```Error
+2024-08-09T06:21:37.712646207Z Unable to connect to the server: dial tcp: lookup aks-test.hcp.westeurope.azmk8s.io: i/o timeout
+2024-10-01T11:26:17.498523756Z Unable to connect to the server: dial tcp 10.146.34.10:443: i/o timeout
+```
+**Resolution**:
+In this case, there is a Network/Calico policy or NSG that didn't allow dataprotection-microsoft pods to communicate with the API server. 
+You should allow the dataprotection-microsoft namespace, and then reinstall the extension.
+
+
 ## Backup Extension post installation related errors
 
 These error codes appear due to issues on the Backup Extension installed in the AKS cluster.

articles/container-apps/networking.md

@@ -286,9 +286,6 @@ Azure networking policies are supported with the public network access flag.
 
 ### <a name="private-endpoint"></a>Private endpoint (preview)
 
-> [!NOTE]
-> This feature is supported for all public regions. Government and China regions aren't supported.
-
 Azure private endpoint enables clients located in your private network to securely connect to your Azure Container Apps environment through Azure Private Link. A private link connection eliminates exposure to the public internet. Private endpoints use a private IP address in your Azure virtual network address space. 
 
 This feature is supported for both Consumption and Dedicated plans in workload profile environments.

articles/data-factory/connector-hbase.md

@@ -44,9 +44,9 @@ For more information about the network security mechanisms and options supported
 
 [!INCLUDE [data-factory-v2-connector-get-started](includes/data-factory-v2-connector-get-started.md)]
 
-## Create a linked service to Hbase using UI
+## Create a linked service to HBase using UI
 
-Use the following steps to create a linked service to Hbase in the Azure portal UI.
+Use the following steps to create a linked service to HBase in the Azure portal UI.
 
 1. Browse to the Manage tab in your Azure Data Factory or Synapse workspace and select Linked Services, then click New:
 
@@ -58,14 +58,14 @@ Use the following steps to create a linked service to Hbase in the Azure portal
 
     :::image type="content" source="media/doc-common-process/new-linked-service-synapse.png" alt-text="Screenshot of creating a new linked service with Azure Synapse UI.":::
 
-2. Search for Hbase and select the Hbase connector.
+2. Search for HBase and select the HBase connector.
 
-   :::image type="content" source="media/connector-hbase/hbase-connector.png" alt-text="Screenshot of the Hbase connector.":::    
+   :::image type="content" source="media/connector-hbase/hbase-connector.png" alt-text="Screenshot of the HBase connector.":::    
 
 
 1. Configure the service details, test the connection, and create the new linked service.
 
-   :::image type="content" source="media/connector-hbase/configure-hbase-linked-service.png" alt-text="Screenshot of linked service configuration for Hbase.":::
+   :::image type="content" source="media/connector-hbase/configure-hbase-linked-service.png" alt-text="Screenshot of linked service configuration for HBase.":::
 
 ## Connector configuration details
 

articles/frontdoor/end-to-end-tls.md

@@ -29,10 +29,10 @@ Azure Front Door offloads the TLS sessions at the edge and decrypts client reque
 
 ## Supported TLS versions
 
-Azure Front Door supports two versions of the TLS protocol: TLS versions 1.2 and 1.3. All Azure Front Door profiles created after September 2019 use TLS 1.2 as the default minimum with TLS 1.3 enabled, with support for TLS 1.0 and TLS 1.1 for backward compatibility. Currently, Azure Front Door doesn't support client/mutual authentication (mTLS).
+Azure Front Door supports two versions of the TLS protocol: TLS versions 1.2 and 1.3. All Azure Front Door profiles created after September 2019 use TLS 1.2 as the default minimum with TLS 1.3 enabled. Currently, Azure Front Door doesn't support client/mutual authentication (mTLS).
 
 > [!IMPORTANT]
-> As of March 1, 2025, TLS 1.0 and 1.1 are disallowed on new Azure Front Door profiles. If you didn't disable TLS 1.0 and 1.1 on legacy settings before this date, they'll still work temporarily but will be disabled in the future.
+> As of March 1, 2025, TLS 1.0 and 1.1 are not allowed on new Azure Front Door profiles. If you didn't disable TLS 1.0 and 1.1 on legacy settings before this date, they'll still work temporarily but will be updated to TLS 1.2 in the future.
 
 You can configure the minimum TLS version in Azure Front Door in the custom domain HTTPS settings using the Azure portal or the [Azure REST API](/rest/api/frontdoorservice/frontdoor/frontdoors/createorupdate#minimumtlsversion). For a minimum TLS version 1.2, the negotiation will attempt to establish TLS 1.3 and then TLS 1.2. When Azure Front Door initiates TLS traffic to the origin, it will attempt to negotiate the best TLS version that the origin can reliably and consistently accept. Supported TLS versions for origin connections are TLS 1.2 and TLS 1.3.
 

articles/frontdoor/front-door-faq.yml

@@ -267,7 +267,7 @@ sections:
         answer: |
           Front Door uses TLS 1.2 as the minimum version for all profiles created after September 2019.
 
-          You can choose to use TLS 1.0, 1.1, 1.2 or 1.3 with Azure Front Door. To learn more, read the [Azure Front Door end-to-end TLS](concept-end-to-end-tls.md) article.
+          You can choose to use TLS 1.2 or 1.3 with Azure Front Door. To learn more, read the [Azure Front Door end-to-end TLS](concept-end-to-end-tls.md) article.
 
   - name: Billing
     questions:

articles/hdinsight/component-version-validation-error-arm-templates.md

@@ -26,7 +26,7 @@ When you're using [templates or automation tools](/azure/hdinsight/hdinsight-had
 | Hadoop | 3.1 |- |3.3|
 | Spark |2.4 |3.1|3.3|
 | Kafka |2.1|2.4|3.2|
-| Hbase | 2.1| -|2.4|
+| HBase | 2.1| -|2.4|
 | InteractiveHive |3.1 |3.1|3.1|
 
 This value enables you to successfully create HDInsight clusters. The following snippet shows how to add the component version in the template:

articles/hdinsight/hbase/apache-hbase-migrate-hdinsight-5-1-new-storage-account.md

@@ -76,7 +76,7 @@ Use these detailed steps and commands to migrate your Apache HBase cluster with
 
 1. Stop ingestion to the source HBase cluster.
 
-1. Check Hbase hbck to verify cluster health
+1. Check HBase hbck to verify cluster health
 
    1. Verify HBCK Report page on HBase UI.  Healthy cluster does not show any inconsistencies
 
@@ -122,7 +122,7 @@ Use these detailed steps and commands to migrate your Apache HBase cluster with
       >
       > For more information on connecting to and using Ambari, see [Manage HDInsight clusters by using the Ambari Web UI](../hdinsight-hadoop-manage-ambari.md).
       >
-      > Stopping HBase in the previous steps mentioned how Hbase avoids creating new master proc WALs.
+      > Stopping HBase in the previous steps mentioned how HBase avoids creating new master proc WALs.
 
 1. If your source HBase cluster doesn't have the [Accelerated Writes](apache-hbase-accelerated-writes.md) feature, skip this step. For source HBase clusters with Accelerated Writes, back up the WAL directory under HDFS by running the following commands from an SSH session on any source cluster Zookeeper node or worker node.
 
@@ -243,7 +243,7 @@ You can download AzCopy from [Get started with AzCopy](../../storage/common/stor
 ## Troubleshooting
 
 ### Use case 1: 
-If Hbase masters and region servers up and regions stuck in transition, or only one region i.e. `hbase:meta` region is assigned, and waiting for other regions to assign
+If HBase masters and region servers up and regions stuck in transition, or only one region i.e. `hbase:meta` region is assigned, and waiting for other regions to assign
 
 **Solution:** 
 

articles/hdinsight/hbase/apache-hbase-migrate-hdinsight-5-1.md

@@ -74,7 +74,7 @@ Use these detailed steps and commands to migrate your Apache HBase cluster.
 
 1. Stop ingestion to the source HBase cluster.
 
-1. Check Hbase hbck to verify cluster health
+1. Check HBase hbck to verify cluster health
 
    1. Verify HBCK Report page on HBase UI.  Healthy cluster doesn't show any inconsistencies
    :::image type="content" source="./media/apache-hbase-migrate-new-version/verify-hbck-report.png" alt-text="Screenshot showing how to verify HBCK report." lightbox="./media/apache-hbase-migrate-new-version/verify-hbck-report.png":::
@@ -83,7 +83,7 @@ Use these detailed steps and commands to migrate your Apache HBase cluster.
 1. Note down number of regions in online at source cluster, so that the number can be referred at destination cluster after the migration. 
    :::image type="content" source="./media/apache-hbase-migrate-new-version/total-number-of-regions.png" alt-text="Screenshot showing total number of regions." lightbox="./media/apache-hbase-migrate-new-version/total-number-of-regions.png":::
 
-1. If replication enabled on the cluster, stop and reenable the replication on destination cluster after migration. For more information, see [Hbase replication guide](/azure/hdinsight/hbase/apache-hbase-replication/)  
+1. If replication enabled on the cluster, stop and reenable the replication on destination cluster after migration. For more information, see [HBase replication guide](/azure/hdinsight/hbase/apache-hbase-replication/)  
 
 1. Flush the source HBase cluster you're upgrading.
 
@@ -269,7 +269,7 @@ Mandatory argument for the above command:
 ## Troubleshooting
 
 ### Use case 1: 
-If Hbase masters and region servers up and regions stuck in transition or only one region, for example, `hbase:meta` region is assigned. Waiting for other regions to assign
+If HBase masters and region servers up and regions stuck in transition or only one region, for example, `hbase:meta` region is assigned. Waiting for other regions to assign
 
 **Solution:**
 

articles/hdinsight/hbase/apache-hbase-tutorial-get-started-linux.md

@@ -202,7 +202,7 @@ You can query data in HBase tables by using [Apache Hive](https://hive.apache.or
 
 1. To exit your ssh connection, use `exit`.
 
-### Separate Hive and Hbase Clusters
+### Separate Hive and HBase Clusters
 
 The Hive query to access HBase data need not be executed from the HBase cluster. Any cluster that comes with Hive (including Spark, Hadoop, HBase, or Interactive Query) can be used to query HBase data, provided the following steps are completed:
 
@@ -214,7 +214,7 @@ The Hive query to access HBase data need not be executed from the HBase cluster.
 HBase data can also be queried from Hive using ESP-enabled HBase: 
 
 1. When following a multi-cluster pattern, both clusters must be ESP-enabled. 
-2. To allow Hive to query HBase data, make sure that the `hive` user is granted permissions to access the HBase data via the Hbase Apache Ranger plugin
+2. To allow Hive to query HBase data, make sure that the `hive` user is granted permissions to access the HBase data via the HBase Apache Ranger plugin
 3. When you use separate, ESP-enabled clusters, the contents of `/etc/hosts` from the HBase cluster headnodes must be appended to `/etc/hosts` of the Hive cluster headnodes and worker nodes. 
 > [!NOTE]
 > After you scale either clusters, `/etc/hosts` must be appended again

articles/hdinsight/hdinsight-hadoop-create-linux-clusters-with-secure-transfer-storage.md

@@ -41,7 +41,7 @@ If you accidentally enabled the 'Require secure transfer' option after creating
 
 `com.microsoft.azure.storage.StorageException: The account being accessed does not support http.`
 
-For Hbase clusters only, you can try the following steps to restore the cluster functionality:
+For HBase clusters only, you can try the following steps to restore the cluster functionality:
 1. Stop HBase from Ambari.
 2. Stop HDFS from Ambari.
 3. In Ambari, navigate to HDFS --> Configs --> Advanced --> fs.defaultFS