From 783f3e4641c3034d78482dd13bac4d1dca974699 Mon Sep 17 00:00:00 2001
From: Pablo Martin <pablo.martin@superhog.com>
Date: Mon, 12 Feb 2024 15:08:32 +0100
Subject: [PATCH] instructions on PBI Gateway

---
 human-script.md | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 47 insertions(+), 1 deletion(-)

diff --git a/human-script.md b/human-script.md
index b295df5..a240c40 100644
--- a/human-script.md
+++ b/human-script.md
@@ -556,10 +556,56 @@ Follow this to deploy the entire data infra.
   echo "Finished."
   ```
 
-- Visit http://airbyte-<your-env>.<your-env>.data.superhog.com. If you are prompted for user and password, it means Airbyte is running properly and is reachable.
+- Visit <http://airbyte-><your-env>.<your-env>.data.superhog.com. If you are prompted for user and password, it means Airbyte is running properly and is reachable.
 
 ## 6. Power BI
 
+### 6.1 Deploying Power BI VM
+
+- We need to deploy a Windows VM.
+- Create the VM
+  - Basic settings
+    - Name it: `pbi-gateway-<your-env>`
+    - Use Windows Server 2022 Datacenter: Azure Edition
+    - Use Size: `Standard_DS1_v2`
+    - Use username: `datagatewayadmin`
+    - Set a good password and note it down
+    - Select the option `None` for Public inbound ports.
+  - Disk settings
+    - Defaults are fine. This barely needs any disk.
+  - Networking
+    - Attach to the virtual network `superhog-data-vnet-<your-env>`
+    - Attach to the subnet `services-subnet`
+    - For field `Public IP` set value `None`
+    - For setting `NIC network security group` select option `None`
+  - Management settings
+    - Defaults are fine.
+  - Monitoring
+    - Defaults are fine.
+  - Advanced
+    - Defaults are fine.
+  - Add tags:
+    - `team: data`
+    - `environment: <your-env>`
+    - `project: pbi`
+- Try to connect with RDP at `pbi-gateway-<your-env>.<your-env>.data.superhog.com`.
+
+### 6.2 Installing Power BI Data Gateway
+
+- Login the VM.
+- Follow the instructions here to download the installer in the VM and set it up: <https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install>
+- You will need to provide an account and credentials. It would be ideal to use a service account, and not personal accounts, to make the gateway independent of any single user.
+- Once you login:
+  - Name the gateway `data-gateway-<your-env>`
+  - Set up a recovery key and store it safely
+- Next, download these file on the VM and install it: <https://github.com/npgsql/npgsql/releases/download/v4.0.10/Npgsql-4.0.10.msi>
+  - ATTENTION! During the installation process, you get to select if you want to activate the `Npgsql GAC Installation`. This option comes deactivated by default. You must turn it on. Click on it and select the `Will be installed on local hard drive` option.
+- Finally, a note: if you want to use this gateway to connect to our PostgreSQL DWH (which you most probably want), you will need to disable forced TLS/SSL in the config of the PostgreSQL instance. This is because PBI is unable to use an SSL connection.
+  - To do this, go to the PostgreSQL isntance page on the Azure Portal.
+  - Click on the `Server parameters` section.
+  - Turn the `require_secure_transport` parameter to `Off`.
+- Once you are done, you should be able to visit the PBI Service (the online UI), visit the gateways page in settings and see the gateway listed in the `On-premises data gateways` section.
+
 ## 7. dbt
 
 ## 8. Status monitoring