Skip to content

Commit

Permalink
Merge branch 'master' of https://github.com/ctesta-oneillmsft/asa-vtd
Browse files Browse the repository at this point in the history
  • Loading branch information
@joelhulen
joelhulen committed Nov 27, 2020
2 parents 2deab50 + 179b18f commit dda227c
Showing 1 changed file with 20 additions and 22 deletions.
42 changes: 20 additions & 22 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -108,14 +108,10 @@ We highly recommend executing the PowerShell scripts on an Azure Virtual Machine

![Download the RDP file to connect to the Power BI virtual machine.](media/azure-vm-connect-2.png "Download RDP File")

7. Open the RDP file and select **Connect** to access the virtual machine. When prompted for credentials, enter `labuser` for the username and the password you chose.
7. Open the RDP file and select **Connect** to access the virtual machine. When prompted for credentials, enter `labuser` for the username and the password you chose. Select the option to allow the security certificate when prompted.

![Connect to a remote host.](media/azure-vm-connect-3.png "Connect to a remote host")

Click Yes to connect despite security certificate errors when prompted.

![The Yes button is highlighted.](media/rdp-connect-certificate.png "Remote Desktop Connection")

### Task 3: Create Azure Synapse Analytics workspace

1. Deploy the workspace through the following Azure ARM template (press the button below):
Expand All @@ -126,14 +122,13 @@ We highly recommend executing the PowerShell scripts on an Azure Virtual Machine

- **Subscription**: Select your desired subscription for the deployment.
- **Resource group**: Select the resource group you previously created.
- **Region**: The datacenter where your Azure Synapse environment will be created.

> **Important**: The `Region` field under 'Parameters' will list the Azure regions where Azure Synapse Analytics is available as of November 2020. This will help you find a region where the service is available without being limited to where the resource group is defined.
- **Unique Suffix**: This unique suffix will be used naming resources that will created as part of your deployment. Make sure you follow correct Azure [Resource naming](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging#resource-naming) conventions.
- **SQL Administrator Login Password**: Provide a strong password for the SQLPool that will be created as part of your deployment. [Visit here](https://docs.microsoft.com/en-us/sql/relational-databases/security/password-policy?view=sql-server-ver15#password-complexity) to read about password rules in place. Your password will be needed during the next steps. Make sure you have your password noted and secured.
- **Location**: The datacenter where your Azure Synapse environment will be created.

> **Important**: The `location` field under 'Settings' will list the Azure regions where Azure Synapse Analytics (Preview) is available as of September 2020. This will help you find a region where the service is available without being limited to where the resource group is defined.
3. Select the **Review + create** button, then **Create**. The provisioning of your deployment resources will take approximately 13 minutes. **Wait** until provisioning successfully completes before continuing. You will need the resources in place before running the scripts below.
3. Check the **I agree to the terms and conditions stated above**, then select the **Purchase** button. The provisioning of your deployment resources will take approximately 13 minutes. **Wait** until provisioning successfully completes before continuing. You will need the resources in place before running the scripts below.

> **Note**: You may experience a deployment step failing in regards to Role Assignment. This error may safely be ignored.
Expand All @@ -150,8 +145,6 @@ The entire script will take between 1.5 and 2 hours to complete. Major steps inc

### Task 1: Pre-requisites

Install these pre-requisites on your **deployment VM** before continuing.

- Install VC Redist: <https://aka.ms/vs/15/release/vc_redist.x64.exe>
- Install MS ODBC Driver 17 for SQL Server: <https://www.microsoft.com/download/confirmation.aspx?id=56567>
- Install SQL CMD x64: <https://go.microsoft.com/fwlink/?linkid=2082790>
Expand All @@ -161,9 +154,7 @@ Install these pre-requisites on your **deployment VM** before continuing.

### Task 2: Download artifacts and install PowerShell modules

Perform all of the steps below from your **deployment VM**:

1. Open a PowerShell Window as an administrator, run the following command to download the artifacts
1. From your **lab VM**, open a PowerShell Window as an administrator, run the following command to download the artifacts

```powershell
mkdir c:\labfiles
Expand All @@ -186,14 +177,20 @@ Perform all of the steps below from your **deployment VM**:
Install-Module -Name Az -AllowClobber -Scope CurrentUser
}
```
<<<<<<< HEAD
> [!Note]: You may be prompted to install NuGet providers, and recieve a prumpt that you are installing the module drom an untrusted repository. Select **Yes** in both instances to proceed with the setup
=======
> [!Note]: You may be prompted to install NuGet providers, and recieve a prompt that you are installing the module from an untrusted repository. Select **Yes** followed by **Yes to All** respectively to proceed with the setup
>>>>>>> 179b18fb29219873deb1f7f6eee45ef22181bd63
* Install `Az.CosmosDB` module
```powershell
Install-Module -Name Az.CosmosDB -AllowClobber
```
> [!Note]: You recieve a prompt that you are installing the module from an untrusted repository. Select **Yes to All** to proceed with the setup.
* Install `sqlserver` module
Expand All @@ -206,19 +203,19 @@ Perform all of the steps below from your **deployment VM**:
```powershell
Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
```
**IMPORTANT**
* **Close the Windows PowerShell window** so you can import the newly installed Az.CosmosDB cmdlet.
### Task 3: Execute setup scripts
Perform all of the steps below from your **deployment VM**:
* Open Windows PowerShell as an Administrator and execute the following:
* From your **lab VM**, open Windows PowerShell as an Administrator and execute the following:
```powershell
Set-ExecutionPolicy Unrestricted
```
> [!Note]: You recieve a prompt that you are installing the module from an untrusted repository. Select **Yes to All** to proceed with the setup.
* Execute the following to import the `Az.CosmosDB` module:
```powershell
Expand All @@ -232,6 +229,9 @@ Perform all of the steps below from your **deployment VM**:
```
* Execute `Connect-AzAccount` and sign in to your Microsoft user account when prompted.
> [!WARNING]: You may recieve the message "TenantId 'xxxxxx-xxxx-xxxx-xxxx' contains more than one active subscription. First one will be selected for further use. You can ignore this at this point, but if you want to select another subscription, use Set-AzContext". In which case you can run ```powershell Set-AzContext SubsciptionName``` to select the subscription you wish to use.
* Execute `az login` and sign in to your Microsoft user account when prompted.
> If you receive the following error, and have already closed and re-opened the PowerShell window, you need to restart your computer and restart the steps in this task: `The term 'az' is not recognized as the name of a cmdlet, function, script file, or operable program`.
Expand All @@ -240,9 +240,7 @@ Perform all of the steps below from your **deployment VM**:
1. You will be prompted to setup your Azure PowerShell and Azure CLI context.
2. If you have mroe than one Azure Subscription, you will be prompted to enter the name of your desired Azure Subscription. You can copy and paste the value from the list to select one. For example:
![A subscription is copied and pasted into the text entry.](media/select-desired-subscription.png "Select desired subscription")
2. You may be prompted to enter the name of your desired Azure Subscription. You can copy and paste the value from the list to select one.
3. Enter the name of the resource group you created at the beginning of the environment setup (such as `synapse-in-a-day-demos`). This will make sure automation runs against the correct environment you provisioned in Azure.
Expand Down

0 comments on commit dda227c

Please sign in to comment.