Fix for timeout during service principal creation (#511)

* Fix for timeout during service principal creation

On slower hardware, many of the cmdlets can take longer to run, causing premature expiration of a timeout and failure to complete. This is one of possible multiple timeouts that needs to be bumped up. The default in the New-AzureBridgeServicePrincipal cmdlet is 300 seconds. This commit increases it to 1800.

* Add additional timeout increase

Registration/RegisterWithAzure.psm1

@@ -1246,7 +1246,7 @@ Function New-ServicePrincipal{
         try
         {
             Log-Output "Creating Azure Active Directory service principal in tenant '$TenantId' Attempt $currentAttempt of $maxAttempt"
-            $servicePrincipal = Invoke-Command -Session $PSSession -ScriptBlock { New-AzureBridgeServicePrincipal -RefreshToken $using:RefreshToken -AzureEnvironment $using:AzureEnvironmentName -TenantId $using:TenantId }
+            $servicePrincipal = Invoke-Command -Session $PSSession -ScriptBlock { New-AzureBridgeServicePrincipal -RefreshToken $using:RefreshToken -AzureEnvironment $using:AzureEnvironmentName -TenantId $using:TenantId -TimeoutInSeconds 1800}
             Log-Output "Service principal created and Azure bridge configured. ObjectId: $($servicePrincipal.ObjectId)"
             return $servicePrincipal
         }
@@ -1357,7 +1357,7 @@ function Activate-AzureStack{
     {
         try
         {
-            $activation = Invoke-Command -Session $session -ScriptBlock { New-AzureStackActivation -ActivationKey $using:ActivationKey }
+            $activation = Invoke-Command -Session $session -ScriptBlock { New-AzureStackActivation -ActivationKey $using:ActivationKey -TimeoutInSeconds 1800}
             break
         }
         catch