Merge pull request #263773 from MicrosoftDocs/main

1/22 11:00 AM IST Publish

Author: Saisang

articles/azure-monitor/app/asp-net-exceptions.md

@@ -4,7 +4,7 @@ description: Capture exceptions from ASP.NET apps along with request telemetry.
 ms.topic: conceptual
 ms.devlang: csharp
 ms.custom: devx-track-csharp
-ms.date: 11/15/2022
+ms.date: 01/31/2024
 ms.reviewer: mmcc
 ---
 

articles/azure-monitor/app/resource-manager-app-resource.md

@@ -2,9 +2,9 @@
 title: Resource Manager template samples for Application Insights resources
 description: Sample Azure Resource Manager templates to deploy Application Insights resources in Azure Monitor.
 ms.topic: sample
-ms.date: 11/14/2022
+ms.date: 01/31/2024
 ms.custom: ignite-fall-2021, devx-track-arm-template
-ms.reviewer: vitalyg
+ms.reviewer: cogoodson
 ---
 
 # Resource Manager template samples for creating Application Insights resources

articles/azure-monitor/app/telemetry-channels.md

@@ -2,7 +2,7 @@
 title: Telemetry channels in Application Insights | Microsoft Docs
 description: How to customize telemetry channels in Application Insights SDKs for .NET and .NET Core.
 ms.topic: conceptual
-ms.date: 05/14/2019
+ms.date: 01/31/2024
 ms.devlang: csharp
 ms.custom: devx-track-csharp, devx-track-dotnet
 ms.reviewer: mmcc

articles/azure-monitor/app/usage-funnels.md

@@ -2,7 +2,7 @@
 title: Application Insights funnels
 description: Learn how you can use funnels to discover how customers are interacting with your application.
 ms.topic: conceptual
-ms.date: 11/15/2022
+ms.date: 01/31/2024
 ms.reviewer: mmcc
 ---
 

articles/azure-resource-manager/bicep/deploy-github-actions.md

@@ -1,18 +1,14 @@
 ---
 title: Deploy Bicep files by using GitHub Actions
 description: In this quickstart, you learn how to deploy Bicep files by using GitHub Actions.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
-ms.date: 08/22/2022
+ms.date: 01/19/2024
 ms.custom: github-actions-azure, devx-track-bicep
 ---
 
 # Quickstart: Deploy Bicep files by using GitHub Actions
 
-[GitHub Actions](https://docs.github.com/en/actions) is a suite of features in GitHub to automate your software development workflows.
-
-In this quickstart, you use the [GitHub Actions for Azure Resource Manager deployment](https://github.com/marketplace/actions/deploy-azure-resource-manager-arm-template) to automate deploying a Bicep file to Azure.
+[GitHub Actions](https://docs.github.com/en/actions) is a suite of features in GitHub to automate your software development workflows. In this quickstart, you use the [GitHub Actions for Azure Resource Manager deployment](https://github.com/marketplace/actions/deploy-azure-resource-manager-arm-template) to automate deploying a Bicep file to Azure.
 
 It provides a short introduction to GitHub actions and Bicep files. If you want more detailed steps on setting up the GitHub actions and project, see [Deploy Azure resources by using Bicep and GitHub Actions](/training/paths/bicep-github-actions).
 
@@ -26,38 +22,47 @@ It provides a short introduction to GitHub actions and Bicep files. If you want
 
 Create a resource group. Later in this quickstart, you'll deploy your Bicep file to this resource group.
 
+# [CLI](#tab/CLI)
+
 ```azurecli-interactive
 az group create -n exampleRG -l westus
 ```
 
+# [PowerShell](#tab/PowerShell)
+
+```azurepowershell-interactive
+New-AzResourceGroup -Name exampleRG -Location westus
+```
+
+---
+
 ## Generate deployment credentials
 
 # [Service principal](#tab/userlevel)
 
-Your GitHub Actions run under an identity. Use the [az ad sp create-for-rbac](/cli/azure/ad/sp#az-ad-sp-create-for-rbac) command to create a [service principal](../../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) for the identity.
-
-Replace the placeholder `myApp` with the name of your application. Replace `{subscription-id}` with your subscription ID.
+Your GitHub Actions run under an identity. Use the [az ad sp create-for-rbac](/cli/azure/ad/sp#az-ad-sp-create-for-rbac) command to create a [service principal](../../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) for the identity. Grant the service principal the contributor role for the resource group created in the previous session so that the GitHub action with the identity can create resources in this resource group. It is recommended that you grant minimum required access.
 
 ```azurecli-interactive
-az ad sp create-for-rbac --name myApp --role contributor --scopes /subscriptions/{subscription-id}/resourceGroups/exampleRG --sdk-auth
+az ad sp create-for-rbac --name {app-name} --role contributor --scopes /subscriptions/{subscription-id}/resourceGroups/exampleRG --json-auth
 ```
 
-> [!IMPORTANT]
-> The scope in the previous example is limited to the resource group. We recommend that you grant minimum required access.
+Replace the placeholder `{app-name}` with the name of your application. Replace `{subscription-id}` with your subscription ID.
 
-The output is a JSON object with the role assignment credentials that provide access to your App Service app similar to below. Copy this JSON object for later. You'll only need the sections with the `clientId`, `clientSecret`, `subscriptionId`, and `tenantId` values.
+The output is a JSON object with the role assignment credentials that provide access to your App Service app similar to below. 
 
 ```output
   {
     "clientId": "<GUID>",
     "clientSecret": "<GUID>",
     "subscriptionId": "<GUID>",
     "tenantId": "<GUID>",
-    (...)
+    ...
   }
 ```
-# [Open ID Connect](#tab/openid)
 
+Copy this JSON object for later. You'll only need the sections with the `clientId`, `clientSecret`, `subscriptionId`, and `tenantId` values. Make sure you don't have an extra comma at the end of the last line, for example, the `tenantId` line in the preceding example, or else it will result in an invalid JSON file. You will get an error during the deployment saying "Login failed with Error: Content is not a valid JSON object. Double check if the 'auth-type' is correct."
+
+# [Open ID Connect](#tab/openid)
 
 Open ID Connect is an authentication method that uses short-lived tokens. Setting up [OpenID Connect with GitHub Actions](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect) is more complex process that offers hardened security.
 
@@ -107,7 +112,7 @@ Open ID Connect is an authentication method that uses short-lived tokens. Settin
 
 # [Service principal](#tab/userlevel)
 
-Create secrets for your Azure credentials, resource group, and subscriptions.
+Create secrets for your Azure credentials, resource group, and subscriptions. You will use these secrets in the [Create workflow](#create-workflow) section.
 
 1. In [GitHub](https://github.com/), navigate to your repository.
 
@@ -164,23 +169,22 @@ To create a workflow, take the following steps:
     # [Service principal](#tab/userlevel)
 
     ```yml
+    name: Deploy Bicep file
     on: [push]
-    name: Azure ARM
     jobs:
       build-and-deploy:
         runs-on: ubuntu-latest
         steps:
 
-          # Checkout code
-        - uses: actions/checkout@main
+        - name: Checkout code
+          uses: actions/checkout@main
 
-          # Log into Azure
-        - uses: azure/login@v1
+        - name: Log into Azure
+          uses: azure/login@v1
           with:
             creds: ${{ secrets.AZURE_CREDENTIALS }}
 
-          # Deploy Bicep file
-        - name: deploy
+        - name: Deploy Bicep file
           uses: azure/arm-deploy@v1
           with:
             subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION }}
@@ -238,17 +242,16 @@ To create a workflow, take the following steps:
 
 
 
-1. Select **Start commit**.
+1. Select **Commit changes**.
 1. Select **Commit directly to the main branch**.
 1. Select **Commit new file** (or **Commit changes**).
 
 Updating either the workflow file or Bicep file triggers the workflow. The workflow starts right after you commit the changes.
 
 ## Check workflow status
 
-1. Select the **Actions** tab. You'll see a **Create deployStorageAccount.yml** workflow listed. It takes 1-2 minutes to run the workflow.
-1. Select the workflow to open it.
-1. Select **Run ARM deploy** from the menu to verify the deployment.
+1. Select the **Actions** tab. You'll see a **Create deployBicepFile.yml** workflow listed. It takes 1-2 minutes to run the workflow.
+1. Select the workflow to open it, and verify the `Status` is `Success`.
 
 ## Clean up resources
 

articles/hdinsight/hdinsight-hadoop-create-linux-clusters-azure-powershell.md

@@ -38,7 +38,7 @@ To create an HDInsight cluster by using Azure PowerShell, you must complete the
 
 The following script demonstrates how to create a new cluster:
 
-[!code-powershell[main](../../powershell_scripts/hdinsight/create-cluster/create-cluster.ps1?range=5-71)]
+[!code-powershell[main](../../azure_powershell_scripts/hdinsight/create-cluster/create-cluster.ps1?range=5-82)]
 
 The values you specify for the cluster login are used to create the Hadoop user account for the cluster. Use this account to connect to services hosted on the cluster such as web UIs or REST APIs.
 

articles/sap/workloads/dbms-guide-oracle.md

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure
-ms.date: 12/15/2023
+ms.date: 01/21/2024
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 ---
@@ -58,9 +58,10 @@ Installing or migrating existing SAP on Oracle systems to Azure, the following d
 5.  ASM removes the requirement for Mirror Log. Follow the guidance from Oracle in Note [888626 - Redo log layout for high-end systems](https://launchpad.support.sap.com/#/notes/888626)
 6.  Use ASMLib and don't use udev
 7.  Azure NetApp Files deployments should use Oracle dNFS (Oracle’s own high performance Direct NFS solution)
-8.  Large databases benefit greatly from large SGA sizes. Large customers should deploy on Azure M-series with 4 TB or more RAM size.
+8.  Large Oracle databases benefit greatly from large SGA sizes. Large customers should deploy on Azure M-series with 4 TB or more RAM size.
     - Set Linux Huge Pages to 75% of Physical RAM size
     - Set SGA to 90% of Huge Page size
+    - Set the Oracle parameter USE_LARGE_PAGES = **ONLY** - The value ONLY is preferred over the value TRUE as the value ONLY is suppossed to deliver more consistent and predictable performance. The value TRUE may allocate both large 2MB and standard 4K pages. The value ONLY is going to always force large 2MB pages. If the number of available huge pages is not sufficient or not correctly configured, the database instance is going to fail to start with error code: *ora-27102 :  out of memory Linux_x86_64 Error 12 : cannot allocate memory*. If there is insufficient contiguous memory Oracle the Operating System may need to be restarted and/or the Operating System Huge Page parameters reconfigured
 9.  Oracle Home should be located outside of the “root” volume or disk. Use a separate disk or ANF volume. The disk holding the Oracle Home should be 64GB or larger
 10. The size of the boot disk for large high performance Oracle database servers is important. As a minimum a P10 disk should be used for M-series or E-series. Don't use small disks such as P4 or P6. A small disk can cause performance issues.
 11. Accelerated Networking must be enabled on all VMs. Upgrade to the latest OL release if there are any problems enabling Accelerated Networking

articles/sap/workloads/get-started.md

@@ -7,7 +7,7 @@ author: msjuergent
 manager: bburns
 ms.topic: article
 ms.workload: infrastructure-services
-ms.date: 12/15/2023
+ms.date: 01/21/2023
 ms.author: juergent
 ---
 
@@ -56,7 +56,8 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
-- December 15, 2023: Change recommendations aroudn DIRECTIO and LVM in [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms-guide-oracle.md)
+- January 21, 2024: Change recommendations around LARGEPAGES in [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms-guide-oracle.md)
+- December 15, 2023: Change recommendations around DIRECTIO and LVM in [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms-guide-oracle.md)
 - December 11, 2023: Add RHEL requirements to [HANA third site for multi-target replication](./disaster-recovery-sap-hana.md) and integrating into a Pacemaker cluster.
 - November 20, 2023: Add storage configuration for Mv3 medium memory VMs into the documents [SAP HANA Azure virtual machine Premium SSD storage configurations](./hana-vm-premium-ssd-v1.md), [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md), and [SAP HANA Azure virtual machine Ultra Disk storage configurations](./hana-vm-ultra-disk.md)
 - November 20, 2023: Add supported storage matrix into the document [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms-guide-oracle.md)