Note: Upgrade GPUs or add to an existing node
The following section provides a high-level overview of the process to add a GPU.
The entire scale unit must be shut down, as a rolling GPU upgrade isn't supported. Stop Azure Stack Hub using the steps documented in the Start and stop Azure Stack Hub article.
Add or upgrade the memory on each physical computer using your hardware manufacturer's documentation.
Start Azure Stack Hub using the steps in Start and stop Azure Stack Hub.
Note: Stop Azure Stack Hub
Stop or shut down Azure Stack Hub with the following steps:
1. Prepare all workloads running on your Azure Stack Hub environment's tenant resources for the upcoming shutdown.
2. Open a privileged endpoint session (PEP) from a machine with network access to the Azure Stack Hub ERCS VMs. For instructions, see Using the privileged endpoint in Azure Stack Hub.
3. From the PEP, run:
Stop-AzureStack
Wait for all physical Azure Stack Hub nodes to power off.
Note
You can verify the power status of a physical node by following the instructions from the original equipment manufacturer (OEM) who supplied your Azure Stack Hub hardware.
4. (Optional) If the stop operation times out, you can monitor its progress using the following PowerShell cmdlet:
Get-ActionStatus Stop-AzureStack
Reference:
https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-start-and-stop

Reference:
https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-border-connectivity
https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-network

[email protected]
Reference:
https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-csp-howto-register-tenants?view=azs-2008&tabs=az

1 - Create a JSON file that contains the role definition.
2 - From Azure Cloud shell, run the New-AzRoleDefinition cmdlet.
3 - From the Azure portal, add a role assignment to sub1.

Reference:
https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-registration?view=azs-2008&tabs=az1%2Caz2%2Caz3%2Caz4&pivots=state-disconnected
Topic 3, Trey Research
General Overview
Trey Research is a pharmaceutical company that has an office in Boston.
Existing environment
Identity Environment
The on-premises network contains an Active Directory forest named treyresearch.net. The forest contains a user named User1.
The forest syncs to an Azure AD tenant named treyresearch.net by using Azure AD Connect.
Trey Research has an internal certification authority (CA).
Compute Environment
The datacenter in the Boston office contains a computer named CLIENT1 that runs Windows 10. CLIENT1 is an administrative workstation that connects directly to the Azure Stack Hub integrated system.
Planned changes and Requirements
Planned changes
Trey Research identifies the following planned changes:
Change the Azure Stack Hub integrated system registration to use an Azure subscription named Subscription3 that has a GUID of 12345678-1234-1234-1234-222222222222.
Configure the integrated system to resolve external names by using a DNS Server that has an IP address of 10.100.100.100.
Implement the App Service resource provider and the Event Hubs resource provider on the integrated system/ Publish a custom cloud-init built image of a Linux virtual machine to Azure Stack Hub Marketplace on the integrated system.
Create a new cloudadmin user named User2.
Assign the delegated provider role to User1.
Azure Stack Hub Requirements
Trey Research identifies the following Azure Stack Hub requirements:
Azure Stack Hub integrated system logs must be forwarded to an external security information and event management (SIEM) system named SIEM1. SIEM1 requires TCP with mutual authentication and TLS 1.2 encryption.
A default Microsoft SQL Server instance will host the database of the App Service resource provider.
The infrastructure of the integrated system must be backed up as frequently as possible.
The integrated system backups must be retained for 28 days.
Business Requirements
Minimize software and licensing costs.