More freshness

Author: sethmanheim

azure-stack/operator/azure-stack-diagnostic-test.md

@@ -2,10 +2,9 @@
 title: Validate system state with the Azure Stack Hub validation tool
 description: Learn how to use the Azure Stack Hub validation tool to validate system state.
 author: sethmanheim
-ms.date: 01/23/2024
+ms.date: 01/28/2025
 ms.topic: article
 ms.author: sethm
-ms.reviewer: adshar
 ms.lastreviewed: 01/10/2020
 
 # Intent: As an Azure Stack operator, I want to use the Azure Stack validation tool to validate the system state.
@@ -15,7 +14,7 @@ ms.lastreviewed: 01/10/2020
 
 # Validate Azure Stack Hub system state
 
-As an Azure Stack Hub operator, being able to determine the health and status of your system on demand is essential. The [Azure Stack Hub validation tool (**Test-AzureStack**)](../reference/pep/test-azurestack.md)) is a PowerShell cmdlet that lets you run a series of tests on your system to identify failures if present. You'll typically be asked to run this tool through the [privileged end point (PEP)](azure-stack-privileged-endpoint.md) when you contact Microsoft Customer Services Support (Microsoft Support) with an issue. With the system-wide health and status information at hand, Microsoft Support can collect and analyze detailed logs, focus on the area where the error occurred, and work with you to fix the issue.
+As an Azure Stack Hub operator, being able to determine the health and status of your system on demand is essential. The [Azure Stack Hub validation tool (**Test-AzureStack**)](../reference/pep/test-azurestack.md) is a PowerShell cmdlet that lets you run a series of tests on your system to identify failures if present. You'll typically be asked to run this tool through the [privileged end point (PEP)](azure-stack-privileged-endpoint.md) when you contact Microsoft Customer Services Support (Microsoft Support) with an issue. With the system-wide health and status information at hand, Microsoft Support can collect and analyze detailed logs, focus on the area where the error occurred, and work with you to fix the issue.
 
 ## Running the validation tool and accessing results
 
@@ -50,17 +49,17 @@ Here's an outline of the end-to-end validation testing process:
 
 1. If any tests report **FAIL**, run `Get-AzureStackLog`. For instructions on an integrated system, see how to run [Get-AzureStackLog on Azure Stack Hub integrated systems](azure-stack-get-azurestacklog.md).
 
-   The cmdlet gathers logs generated by Test-AzureStack. We recommend you don't collect logs and contact Microsoft Support instead if tests report **WARN**.
+   The cmdlet gathers logs generated by **Test-AzureStack**. If the tests report **WARN**, we recommend that you don't collect logs, and instead contact Microsoft Support.
 
-1. If you're instructed to run the validation tool by the Microsoft Support, the Microsoft Support representative will request the logs you collected to continue troubleshooting your issue.
+1. If you're instructed to run the validation tool by the Microsoft Support, the Microsoft Support representative requests the logs you collected in order to continue troubleshooting your issue.
 
 ## Tests available
 
-The validation tool lets you run a series of system-level tests and basic cloud scenarios that provide you with insight to the current state, allowing you to fix issues in your system.
+The validation tool lets you run a series of system-level tests and basic cloud scenarios that provide you with insight into the current state, enabling you to fix issues in your system.
 
 ### Cloud infrastructure tests
 
-These low impact tests work on an infrastructure level and provide you with information on various system components and functions. Currently, tests are grouped into the following categories:
+These low impact tests work on an infrastructure level and provide you with information about various system components and functions. Currently, tests are grouped into the following categories:
 
 | Test Category                                        | Argument for -Include and -Ignore |
 | :--------------------------------------------------- | :-------------------------------- |
@@ -132,7 +131,6 @@ The following cloud scenarios are tested by the validation tool:
 ## Parameter considerations
 
 - The parameter **List** can be used to display all available test categories.
-
 - The parameters **Include** and **Ignore** can be used to include or exclude test categories. For more information about these arguments, see the following section.
 
   ```powershell
@@ -144,21 +142,19 @@ The following cloud scenarios are tested by the validation tool:
   ```
 
 - A tenant VM is deployed as part of the cloud scenario tests. You can use **DoNotDeployTenantVm** to disable this VM deployment.
-
-- You need to supply the **ServiceAdminCredential** parameter to run cloud scenario tests as described in the [Use case examples](azure-stack-diagnostic-test.md#use-case-examples) section.
-
+- You must supply the **ServiceAdminCredential** parameter to run cloud scenario tests as described in the [Use case examples](azure-stack-diagnostic-test.md#use-case-examples) section.
 - **BackupSharePath** and **BackupShareCredential** are used when testing infrastructure backup settings as shown in the [Use case examples](azure-stack-diagnostic-test.md#use-case-examples) section.
-
 - **DetailedResults** can be used to get pass/fail/warning information for each test, as well as the overall run. When not specified, **Test-AzureStack** returns **$true** if there are no failures, and **$false** if there are failures.
 - **TimeoutSeconds** can be used to set a specific time for each group to complete.
-
 - The validation tool also supports common PowerShell parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see [About Common Parameters](/powershell/module/microsoft.powershell.core/about/about_commonparameters).  
 
 ## Use case examples
 
+The following examples show how to run the validation tool with different parameters and scenarios.
+
 ### Run validation without cloud scenarios
 
-Run the validation tool without the **ServiceAdminCredential** parameter to skip running cloud scenario tests: 
+Run the validation tool without the **ServiceAdminCredential** parameter to skip running cloud scenario tests:
 
 ```powershell
 New-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred -SessionOption (New-PSSessionOption -Culture en-US -UICulture en-US)
@@ -167,25 +163,25 @@ Test-AzureStack
 
 ### Run validation with cloud scenarios
 
-Supplying the validation tool with the **ServiceAdminCredentials** parameter runs the cloud scenario tests by default: 
+Supplying the validation tool with the **ServiceAdminCredentials** parameter runs the cloud scenario tests by default:
 
 ```powershell
 Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
 Test-AzureStack -ServiceAdminCredential "<Cloud administrator user name>" 
 ```
 
-If you wish to run ONLY cloud scenarios without running the rest of the tests, you can use the **Include** parameter to do so: 
+If you only want to run cloud scenarios without running the rest of the tests, you can use the `Include` parameter:
 
 ```powershell
 Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
 Test-AzureStack -ServiceAdminCredential "<Cloud administrator user name>" -Include AzsScenarios   
 ```
 
-The cloud admin user name must be typed in the UPN format: [email protected] (Microsoft Entra ID). When prompted, type the password to the cloud admin account.
+The cloud admin user name must be typed in the UPN format: `[email protected]` (Microsoft Entra ID). When prompted, type the password to the cloud admin account.
 
 ### Groups
 
-To improve the operator experience, a **Group** parameter has been enabled to run multiple test categories at the same time. Currently, there are three groups defined: **Default**, **UpdateReadiness**, and **SecretRotationReadiness**.
+To improve the operator experience, a **Group** parameter runs multiple test categories at the same time. Currently, there are three groups defined: **Default**, **UpdateReadiness**, and **SecretRotationReadiness**.
 
 - **Default**: Considered to be a standard run of **Test-AzureStack**. This group is run by default if no other groups are selected.
 - **UpdateReadiness**: A check to see if the Azure Stack Hub instance can be updated. When the **UpdateReadiness** group is run, warnings are displayed as errors in the console output, and they should be considered as blockers for the update. The following categories are part of the **UpdateReadiness** group:
@@ -216,39 +212,38 @@ Test-AzureStack -Group UpdateReadiness
 
 ### Run validation tool to test infrastructure backup settings
 
-*Before* configuring infrastructure backup, you can test the backup share path and credential using the **AzsBackupShareAccessibility** test:
+Before configuring infrastructure backup, you can test the backup share path and credential using the **AzsBackupShareAccessibility** test:
 
-  ```powershell
-  Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
-  Test-AzureStack -Include AzsBackupShareAccessibility -BackupSharePath "\\<fileserver>\<fileshare>" -BackupShareCredential $using:backupcred
-  ```
+```powershell
+Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
+Test-AzureStack -Include AzsBackupShareAccessibility -BackupSharePath "\\<fileserver>\<fileshare>" -BackupShareCredential $using:backupcred
+```
 
-*After* configuring backup, you can run **AzsBackupShareAccessibility** to validate the share is accessible from the ERCS:
+After configuring backup, you can run **AzsBackupShareAccessibility** to validate the share is accessible from the ERCS:
 
-  ```powershell
-  Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
-  Test-AzureStack -Include AzsBackupShareAccessibility
-  ```
+```powershell
+Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
+Test-AzureStack -Include AzsBackupShareAccessibility
+```
 
-To test new credentials with the configured backup share, run: 
+To test new credentials with the configured backup share, run:
 
-  ```powershell
-  Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
-  Test-AzureStack -Include AzsBackupShareAccessibility -BackupShareCredential "<PSCredential for backup share>"
-  ```
+```powershell
+Enter-PSSession -ComputerName "<ERCS VM-name/IP address>" -ConfigurationName PrivilegedEndpoint -Credential $localcred 
+Test-AzureStack -Include AzsBackupShareAccessibility -BackupShareCredential "<PSCredential for backup share>"
+```
 
 ### Run validation tool to test network infrastructure
 
 This test checks the connectivity of the network infrastructure bypassing the Azure Stack Hub software defined network (SDN). It demonstrates connectivity from a Public VIP to the configured DNS forwarders, NTP servers, and authentication endpoints. This includes connectivity to Azure when using Microsoft Entra ID as identity provider or the federated server when using AD FS as identity provider.
 
-Include the debug parameter to get a detailed output of the command:
+Include the `-Debug` parameter to get a detailed output of the command:
 
 ```powershell
 Test-AzureStack -Include AzsNetworkInfra -Debug
 ```
 
 ## Next steps
 
-To learn more about Azure Stack Hub diagnostics tools and issue logging, see [Azure Stack Hub Diagnostic log collection](./diagnostic-log-collection.md).
-
-To learn more about troubleshooting, see [Microsoft Azure Stack Hub troubleshooting](azure-stack-troubleshooting.md).
+- For more information about Azure Stack Hub diagnostics tools and issue logging, see [Azure Stack Hub Diagnostic log collection](./diagnostic-log-collection.md)
+- For more information about troubleshooting, see [Microsoft Azure Stack Hub troubleshooting](azure-stack-troubleshooting.md)

azure-stack/user/user-overview.md

@@ -1,15 +1,14 @@
 ---
 title: What is Azure Stack Hub for a user? 
-description: Learn how to use Azure Stack Hub as a developer.
+description: Learn how to use Azure Stack Hub as a user.
 author: sethmanheim
-
 ms.topic: article
-ms.date: 12/2/2020
+ms.date: 01/28/2025
 ms.author: sethm
 ms.reviewer: thoroet
 ms.lastreviewed: 12/2/2020
 
-# Intent: As an Azure Stack Hub user, I wan to learn about how where to find more information developing solutions.
+# Intent: As an Azure Stack Hub user, I want to learn about where to find more information about developing solutions.
 # Keywords: Develop solutions with Azure Stack Hub
 
 ---
@@ -20,9 +19,7 @@ Azure Stack Hub is a hybrid cloud platform that lets you use Azure services from
 
 ## How to use Azure Stack Hub
 
-If you're an Azure Stack Hub operator who manages the infrastructure and offers services, check out the [operator documentation](../operator/index.yml).
-
-If you are an Azure Stack Hub user interested in the Azure Stack Development Kit (ASDK), a single-node deployment of Azure Stack Hub that you can download and use for free, see the [ASDK documentation](../asdk/index.yml).
+If you're an Azure Stack Hub operator who manages the infrastructure and offers services, see the [operator documentation](../operator/index.yml).
 
 ## Next steps