Azure RETL docs [netlify-build]

Author: stayseesong

src/_data/sidenav/main.yml

@@ -185,6 +185,8 @@ sections:
     - section_title: Reverse ETL Source Setup Guides
       slug: connections/reverse-etl/reverse-etl-source-setup-guides
       section:
+      - path: /connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup
+        title: Azure Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup
         title: BigQuery Reverse ETL Setup
       - path: /connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup

src/connections/reverse-etl/index.md

@@ -38,9 +38,10 @@ To add your warehouse as a source:
 > You need to be a user that has both read and write access to the warehouse.
 
 1. Navigate to **Connections > Sources** and select the **Reverse ETL** tab in the Segment app.
-2. Click **Add Reverse ETL source**.
+2. Click **+ Add Reverse ETL source**.
 3. Select the source you want to add. 
 4. Follow the corresponding setup guide for your Reverse ETL source.
+    * [Azure Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup/)
     * [BigQuery Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup/)
     * [Databricks Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup/)
     * [Postgres Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup/)
@@ -49,7 +50,7 @@ To add your warehouse as a source:
 5. Add the account information for your source.  
     * For Snowflake users: Learn more about the Snowflake Account ID [here](https://docs.snowflake.com/en/user-guide/admin-account-identifier.html){:target="_blank"}.
 5. Click **Test Connection** to test to see if the connection works.
-6. Click **Create Source** if the test connection is successful.
+6. Click **Add source** if the test connection is successful.
 
 After you add your data warehouse as a source, you can [add a model](#step-2-add-a-model) to your source.
 

src/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup.md

@@ -0,0 +1,74 @@
+---
+title: Azure Reverse ETL Setup
+---
+
+> info "Public beta"
+> The Azure source for Reverse ETL is in public beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. 
+
+Set up Azure as your Reverse ETL source.
+
+At a high level, when you set up Azure dedicated SQL pools for Reverse ETL, the configured user needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema (`__SEGMENT_REVERSE_ETL`), which requires the configured user to allow write permissions for that schema.
+
+## Required permissions
+Make sure the user you use to connect to Segment has permissions to use that warehouse. You can follow the process below to set up a new user with sufficient permissions for Segment’s use.
+
+> info ""
+> Execute all commands in the database where your data resides, except the first `CREATE LOGIN` command, which you need to execute in the master database.
+
+* To create a login and user for Segment, run:
+    
+    ```
+    CREATE LOGIN SegmentReverseETLLogin WITH PASSWORD = 'Str0ng_password'; -- password of your choice
+    CREATE USER SegmentReverseETLUser FOR LOGIN SegmentReverseETLLogin;
+    ```
+
+* To grant access to the user to read data from all schemas  in the database, run: 
+
+    ```
+    EXEC sp_addrolemember 'db_datareader', 'SegmentReverseETLUser';
+    ```
+
+* To grant Segment access to read from certain schemas, run: 
+
+    ```
+    CREATE ROLE SegmentReadRole;
+    GRANT SELECT ON SCHEMA::[schema_name] TO SegmentReadRole;
+    EXEC sp_addrolemember 'SegmentReadRole', 'SegmentReverseETLUser';
+    ```
+
+* To grant Segment access to create a schema to keep track of the running syncs, run:
+
+    ```
+    GRANT CREATE SCHEMA TO SegmentReverseETLUser;
+    ```
+
+* If you want to create the schema yourself and then give Segment access to it, run:
+
+    ```
+    CREATE SCHEMA  __segment_reverse_etl;
+    GRANT CONTROL ON SCHEMA::__segment_reverse_etl TO SegmentReverseETLUser;
+    GRANT CREATE TABLE ON DATABASE::[database_name] TO SegmentReverseETLUser;
+    ```
+
+## Set up guide
+To set up Azure as your Reverse ETL source:
+1. Log in to your Azure account.
+2. Navigate to your **dedicated SQL pool**. Segment supports both dedicated SQL pool (formerly SQL DW) and dedicated SQL pool in Synapse workspace. 
+3. Navigate to **Settings > Connection strings** and select the **JDBC** tab to find the server, port, and database name. 
+4. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank"}. 
+5. Navigate to **Connections > Sources** and select the **Reverse ETL** tab. 
+6. Click **+ Add Reverse ETL source**. 
+7. Select **Azure** and click **Add Source**. 
+8. Enter the configuration settings for you Azure source based on the information from Step 3. 
+    * Hostname: 
+        * Use `xxxxxxx.sql.azuresynapse.net` if you’re connecting to a dedicated SQL pool in Synapse workspace. 
+        * Use `xxxxxxx.database.windows.net` if you’re connecting to a dedicated SQL pool (formerly SQL DW)
+    * Port: `1433` (default)
+    * Database name: The name of your dedicated SQL pool.
+    * Username: The login name you created with `CREATE LOGIN` in the [required permissions](#required-permissions) section. 
+    * Password: The password that's associated with the login name.
+9. Click **Test Connection** to see if the connection works. If the connection fails, make sure you have the right permissions and credentials, then try again.
+10. Click **Add source** if the test connection is successful. 
+
+Once you've successfully added your Azure source, [add a model](/docs/connections/reverse-etl/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. 
+

src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md

@@ -26,7 +26,7 @@ To set up the Segment BigQuery connector:
 14. Navigate to the Segment UI and paste all the credentials you copied from step 13 into the **Enter your credentials** section.
 19. Enter your **Data Location**.
 20. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again.
-6. Click **Create Source** if the test connection is successful.
+6. Click **Add source** if the test connection is successful.
 
 Once you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl#step-2-add-a-model).
 

src/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup.md

@@ -39,7 +39,7 @@ To set up Databricks as your Reverse ETL source:
 4. Select **SQL Warehouses** and select the warehouse you want to use. Note that Segment doesn't support the `Compute` connection parameters.
 5. Go to the **Connection details** tab and **keep** this page open.
 6. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank”}. 
-7. Navigate to **Connections > Sources > Reverse ETL**.
+7. Navigate to **Connections > Sources** and select the **Reverse ETL** tab.
 8. Click **+ Add Reverse ETL source**. 
 9. Select **Databricks** and click **Add Source**. 
 10. Enter the configuration setting for your Databricks source based on information from step 5
@@ -49,7 +49,7 @@ To set up Databricks as your Reverse ETL source:
     * Token: `<your-token>`
     * Catalog [optional]: `hive_metastore` (default)
 11. Click **Test Connection** to see if the connection works. If the connection fails, make sure you have the right permissions and credentials, then try again.
-12. Click **Create Source** if the test connection is successful. 
+12. Click **Add source** if the test connection is successful. 
 
 > info ""
 > To generate a token, follow the steps listed in the [Databricks docs](https://docs.databricks.com/dev-tools/auth.html#pat){:target="_blank"}. Segment recommends you create a token with no expiration date by leaving the lifetime field empty when creating it. If you already have a token with an expiration date, be sure to keep track of the date and renew it on time.