StackHCI Registration process Improvements ( small pending changes) (#18310)

* removed remote support related change whcih is not ready yet

* updated fairfax Graph API scope

Co-authored-by: Niranjan B <[email protected]>

Author: bniranjanbhat

src/StackHCI/Az.StackHCI.psm1

@@ -154,7 +154,7 @@ $GraphServiceApiScopeAzureChinaCloud = "https://microsoftgraph.chinacloudapi.cn/
 $ServiceEndpointAzureUSGovernment = "https://dp.azurestackhci.azure.us"
 $AuthorityAzureUSGovernment = "https://login.microsoftonline.us"
 $BillingServiceApiScopeAzureUSGovernment = "https://dp.azurestackhci.azure.us/.default"
-$GraphServiceApiScopeAzureUSGovernment = "https://graph.windows.net/.default"
+$GraphServiceApiScopeAzureUSGovernment =  "https://graph.microsoft.us/.default"
 
 $ServiceEndpointAzureGermanCloud = "https://azurestackhci-usage.trafficmanager.de"
 $AuthorityAzureGermanCloud = "https://login.microsoftonline.de"
@@ -4771,7 +4771,7 @@ function New-Directory{
 #>
 function Invoke-DeploymentModuleDownload{
     # Remote Support
-    New-Variable -Name RemoteSupportPackageUri -Value "https://srsqldatasa.blob.core.windows.net/packages" -Option Constant -Scope Script
+    New-Variable -Name RemoteSupportPackageUri -Value "https://remotesupportpackages.blob.core.windows.net/packages" -Option Constant -Scope Script
     $DownloadCacheDirectory = Join-Path $env:Temp "RemoteSupportPkgCache"
 
     $BlobLocation = "$script:RemoteSupportPackageUri/Microsoft.AzureStack.Deployment.RemoteSupport.psm1"

src/StackHCI/ChangeLog.md

@@ -26,12 +26,10 @@
     -Service endpoints are now specified by HCI Cloud services instead of it being hardcoded in the PS module
 * Added support to specify ArcServerResourceGroupName to Register-AzStackHCI cmdlet
     - Now we can specify the resource group into which the ARC resource gets projected using 'ArcServerResourceGroupName' parameter during registration
-* Check ResourceProvider is already registered before attempting to register during Register-AzStackHCI cmdlet
+* Check ResourceProvider is already registered before attempting to register it during Register-AzStackHCI cmdlet
     - Register-AzStackHCI cmdlet now does not take any action if required Resource Providers are already registered. This allows users with Roles who do not have permissions to register resource providers to still perform registration operation
 * Supported for writing event log entries from registration cmdlets
     - Register-AzStackHCI and UnRegister-AzStackHCI flows will now write events to Node log reflecting the status  of registration. Events will be logged under source name "HCI Registration"
-* Updated IMDS Cluster network
-    - To mark Attestation network as "no cluster role" if it only contains the Attestation adapters.
 
 ## Version 1.1.1
 * Updated firewall rules for Attestation network to block all other traffic