Skip to content

Commit 2fd3dca

Browse files
docs: update CustomizeData.md to clarify WAF-aligned deployment instructions
1 parent 1a29d87 commit 2fd3dca

File tree

1 file changed

+12
-13
lines changed

1 file changed

+12
-13
lines changed

documents/CustomizeData.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ If you would like to update the solution to leverage your own data please follow
1010

1111
1. Navigate to the storage account in the resource group you are using for this solution.
1212
2. Open the `data` container
13+
14+
> **Note for WAF-aligned deployments:** If your deployment uses private networking, you'll need to log into a VM within the virtual network to upload files. See [VM login instructions](#how-to-login-to-vm-using-azure-bastion) below.
15+
1316
3. If you have audio files, upload them to `custom_audiodata` folder. If you have call transcript files, upload them to `custom_transcripts` folder.
1417
4. Navigate to the terminal and run the `run_process_data_scripts.sh` to process the new data into the solution with the following commands.
1518
```shell
@@ -21,17 +24,13 @@ If you would like to update the solution to leverage your own data please follow
2124
```
2225
a. resourcegroupname_param - the name of the resource group.
2326

24-
> Note (WAF‑aligned deployments): If you deployed the solution with the WAF / private networking option enabled, you must run the data processing script **from inside the deployed VM (jumpbox / processing VM)** so it can reach the private endpoints. Follow these steps:
25-
>
26-
> 1. Connect to the VM (Azure Bastion, SSH, or RDP depending on OS).
27-
> 2. Ensure the repo (or the `infra/scripts` folder) is present. If not, clone or pull it.
28-
> 3. Open a Bash-compatible shell (Git Bash on Windows, or native bash on Linux).
29-
> 4. Run `az login` (add `--tenant <tenantId>` if required by your org policy).
30-
> 5. Navigate to `infra/scripts` and execute:
31-
> ```bash
32-
> bash run_process_data_scripts.sh <resource-group-name>
33-
> ```
34-
> 6. Replace `<resource-group-name>` with the name of the resource group you deployed (same value used for `resourcegroupname_param`).
35-
>
36-
> Tip: If Azure CLI is not installed on the VM, install it first (see official docs) before running the script.
27+
## How to Login to VM Using Azure Bastion
28+
29+
For WAF-aligned deployments with private networking:
30+
31+
1. Navigate to your VM in the Azure portal
32+
2. Click **Connect****Bastion**
33+
3. Enter your VM credentials and click **Connect**
34+
4. Once connected, use Azure CLI commands to upload files to the storage account
35+
3736

0 commit comments

Comments
 (0)