Merge pull request #15698 from sethmanheim/managedid8-20

Security initiative: managed ids

Author: sethmanheim

AKS-Hybrid/container-storage-interface-files.md

@@ -3,7 +3,7 @@ title: Use Container Storage Interface (CSI) file drivers in AKS enabled by Azur
 description: Learn how to use Container Storage Interface (CSI) drivers to manage files in AKS Arc.
 author: sethmanheim
 ms.topic: how-to
-ms.date: 01/12/2024
+ms.date: 08/20/2024
 ms.author: sethm 
 ms.lastreviewed: 01/14/2022
 ms.reviewer: abha
@@ -33,46 +33,46 @@ If multiple nodes need concurrent access to the same storage volumes in AKS Arc,
 
 1. Make sure the SMB driver is deployed. The SMB CSI driver is installed by default when you create a Kubernetes cluster using the Azure portal or the `az aksarc create` command. If you create a Kubernetes cluster by using `--disable-smb-driver`, you must enable the SMB driver on this cluster using the `az aksarc update` command:
 
-      ```azurecli
-      az aksarc update -n $aksclustername -g $resource_group --enable-smb-driver
-      ```
+   ```azurecli
+   az aksarc update -n $aksclustername -g $resource_group --enable-smb-driver
+   ```
 
 ### [AKS on Azure Stack HCI 22H2 and Windows Server](#tab/22H2)
 
 1. Make sure the SMB driver is deployed. Deploy the driver using the following [Install-AksHciCsiSmb](./reference/ps/install-akshcicsismb.md) PowerShell command:
 
-      ```powershell
-      Install-AksHciCsiSmb -clusterName mycluster
-      ```
+   ```powershell
+   Install-AksHciCsiSmb -clusterName mycluster
+   ```
 
 ---
 
-2. Create Kubernetes secrets to store the credentials required to access SMB shares by running the following command:
+1. Create Kubernetes secrets to store the credentials required to access SMB shares by running the following command:
 
    ```console
    kubectl create secret generic smbcreds --from-literal username=$username --from-literal password=$password --from-literal domain=$domain
    ```
 
-3. Create a storage class using `kubectl` to create a new SMB storage class with the following manifest:
-
-      ```yaml
-      apiVersion: storage.k8s.io/v1
-      kind: StorageClass
-      metadata:
-        name: smb-csi
-      provisioner: smb.csi.akshci.com
-      parameters:
-         source: \\smb-server\share
-         csi.storage.k8s.io/node-stage-secret-name: "smbcreds"
-         csi.storage.k8s.io/node-stage-secret-namespace: "default"
-      reclaimPolicy: Retain  # only Retain is supported
-      volumeBindingMode: Immediate
-      mountOptions:
-        - dir_mode=0777
-        - file_mode=0777
-        - uid=1001
-        - gid=1001
-      ```  
+1. Create a storage class using `kubectl` to create a new SMB storage class with the following manifest:
+
+   ```yaml
+   apiVersion: storage.k8s.io/v1
+   kind: StorageClass
+   metadata:
+     name: smb-csi
+   provisioner: smb.csi.akshci.com
+   parameters:
+      source: \\smb-server\share
+      csi.storage.k8s.io/node-stage-secret-name: "smbcreds"
+      csi.storage.k8s.io/node-stage-secret-namespace: "default"
+   reclaimPolicy: Retain  # only Retain is supported
+   volumeBindingMode: Immediate
+   mountOptions:
+     - dir_mode=0777
+     - file_mode=0777
+     - uid=1001
+     - gid=1001
+   ```  
 
 ### Use NFS drivers
 
@@ -94,7 +94,7 @@ If multiple nodes need concurrent access to the same storage volumes in AKS Arc,
 
 ---
 
-2. Create an NFS storage class using the following manifest:
+1. Create an NFS storage class using the following manifest:
 
       ```yaml
       apiVersion: storage.k8s.io/v1

azure-stack/asdk/asdk-telemetry.md

@@ -4,9 +4,8 @@ description: Learn how to configure Azure Stack telemetry settings using PowerSh
 author: sethmanheim
 
 ms.topic: article
-ms.date: 02/12/2019
+ms.date: 09/05/2024
 ms.author: sethm
-ms.reviewer: misainat
 ms.lastreviewed: 10/15/2019
 
 # Intent: As an ASDK user, I want to learn about Azure Stack telemetry, so I can learn how use it, leverage it, and manage it. 
@@ -101,39 +100,15 @@ Turning off Windows and Azure Stack telemetry disables SQL telemetry. For additi
 ### Enable or disable telemetry after deployment
 
 To enable or disable telemetry after deployment, you need to have access to the Privileged End Point (PEP) which is exposed on the ERCS VMs.
-1.	To Enable: `Set-Telemetry -Enable`
-2.	To Disable: `Set-Telemetry -Disable`
+
+1. To Enable: `Set-Telemetry -Enable`
+1. To Disable: `Set-Telemetry -Disable`
 
 PARAMETER Detail:
 > .PARAMETER Enable - Turn On telemetry data upload
-> 
+>
 > .PARAMETER Disable - Turn Off telemetry data upload  
 
-**Script to enable telemetry:**
-```powershell
-$ip = "<IP ADDRESS OF THE PEP VM>" # You can also use the machine name instead of IP here.
-$pwd= ConvertTo-SecureString "<CLOUD ADMIN PASSWORD>" -AsPlainText -Force
-$cred = New-Object System.Management.Automation.PSCredential ("<DOMAIN NAME>\CloudAdmin", $pwd)
-$psSession = New-PSSession -ComputerName $ip -ConfigurationName PrivilegedEndpoint -Credential $cred -SessionOption (New-PSSessionOption -Culture en-US -UICulture en-US)
-Invoke-Command -Session $psSession {Set-Telemetry -Enable}
-if($psSession)
-{
-    Remove-PSSession $psSession
-}
-```
-
-**Script to disable telemetry:**
-```powershell
-$ip = "<IP ADDRESS OF THE PEP VM>" # You can also use the machine name instead of IP here.
-$pwd= ConvertTo-SecureString "<CLOUD ADMIN PASSWORD>" -AsPlainText -Force
-$cred = New-Object System.Management.Automation.PSCredential ("<DOMAIN NAME>\CloudAdmin", $pwd)
-$psSession = New-PSSession -ComputerName $ip -ConfigurationName PrivilegedEndpoint -Credential $cred -SessionOption (New-PSSessionOption -Culture en-US -UICulture en-US)
-Invoke-Command -Session $psSession {Set-Telemetry -Disable}
-if($psSession)
-{
-    Remove-PSSession $psSession
-}
-```
-
 ## Next steps
-[Start and stop the ASDK](asdk-start-stop.md)
+
+[Start and stop the ASDK](asdk-start-stop.md)