You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documents/CustomizeData.md
+12-13Lines changed: 12 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ If you would like to update the solution to leverage your own data please follow
10
10
11
11
1. Navigate to the storage account in the resource group you are using for this solution.
12
12
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
+
13
16
3. If you have audio files, upload them to `custom_audiodata` folder. If you have call transcript files, upload them to `custom_transcripts` folder.
14
17
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.
15
18
```shell
@@ -21,17 +24,13 @@ If you would like to update the solution to leverage your own data please follow
21
24
```
22
25
a. resourcegroupname_param - the name of the resource group.
23
26
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).
0 commit comments