Skip to content

Commit 96c6ce0

Browse files
docs: Merge pull request #250 from microsoft/bug_bash_pk
fix: Readme file updated
2 parents dd5ef5a + b266132 commit 96c6ce0

File tree

6 files changed

+91
-1
lines changed

6 files changed

+91
-1
lines changed

README.md

Lines changed: 38 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,22 @@ Please check the link [Azure Products by Region](https://azure.microsoft.com/en-
7070

7171
- Embedding model capacity
7272

73+
74+
### Checking Resource Availability by Region
75+
76+
Before deploying, ensure that the required Azure services are available in your region. Below are links to check service availability:
77+
78+
- [Azure Products by Region](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/)
79+
- [Semantic Search Availability](https://learn.microsoft.com/en-us/azure/search/search-region-support)
80+
81+
## **Steps to Check Semantic Search Availability**
82+
1. Open the [Semantic Search Availability](https://learn.microsoft.com/en-us/azure/search/search-region-support) page.
83+
2. Scroll down to the **"Availability by Region"** section.
84+
3. Use the table to find supported regions for **Azure AI Search** and its **Semantic Search** feature.
85+
4. If your target region is not listed, choose a supported region for deployment.
86+
87+
📌 **Note:** Some features may only be available in specific regions, so ensure compatibility before proceeding.
88+
7389
### [Optional]: Quota Recommendations
7490
- The default for the GPT model capacity in deployment is **30k tokens**.
7591
- For optimal performance, it is recommended to increase to **100k tokens**.
@@ -188,7 +204,7 @@ By default this template will use the environment name as the prefix to prevent
188204
Change the Content Understanding Location (allowed values: West US, Sweden Central, Australia East)
189205
190206
```shell
191-
azd env set AZURE_ENV_CU_LOCATION 'West US'
207+
azd env set AZURE_ENV_CU_LOCATION 'westus'
192208
```
193209
194210
Change the Secondary Location (example: eastus2, westus2, etc.)
@@ -235,6 +251,12 @@ azd env set AZURE_ENV_EMBEDDING_MODEL_CAPACITY 80
235251
azd auth login
236252
```
237253
254+
#### To authenticate with Azure Developer CLI (`azd`), use the following command with your **Tenant ID**:
255+
256+
```sh
257+
azd auth login --tenant-id <tenant-id>
258+
259+
238260
2. Provision and deploy all the resources:
239261
240262
```shell
@@ -286,6 +308,21 @@ Additional Steps
286308
287309
Note: Authentication changes can take up to 10 minutes
288310
311+
3. **Deleting Resources After a Failed Deployment**
312+
Follow steps in [Delete Resource Group](./docs/DeleteResourceGroup.md) If your deployment fails and you need to clean up the resources.
313+
314+
## Sample Questions
315+
316+
To help you get started, here are some **Sample Questions** you can ask in the app:
317+
318+
- Total number of calls by date for the last 7 days
319+
- Show average handling time by topics in minutes
320+
- What are the top 7 challenges users reported?
321+
- Give a summary of billing issues
322+
- When customers call in about unexpected charges, what types of charges are they seeing?
323+
324+
These questions serve as a great starting point to explore insights from the data.
325+
</br>
289326
<h2>
290327
</br>
291328
Responsible AI Transparency FAQ

docs/DeleteResourceGroup.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Deleting Resources After a Failed Deployment in Azure Portal
2+
3+
If your deployment fails and you need to clean up the resources manually, follow these steps in the Azure Portal.
4+
5+
---
6+
7+
## **1. Navigate to the Azure Portal**
8+
1. Open [Azure Portal](https://portal.azure.com/).
9+
2. Sign in with your Azure account.
10+
11+
---
12+
13+
## **2. Find the Resource Group**
14+
1. In the search bar at the top, type **"Resource groups"** and select it.
15+
2. Locate the **resource group** associated with the failed deployment.
16+
17+
![Resource Groups](Images/resourcegroup.png)
18+
19+
![Resource Groups](Images/resource-groups.png)
20+
21+
---
22+
23+
## **3. Delete the Resource Group**
24+
1. Click on the **resource group name** to open it.
25+
2. Click the **Delete resource group** button at the top.
26+
27+
![Delete Resource Group](Images/DeleteRG.png)
28+
29+
3. Type the resource group name in the confirmation box and click **Delete**.
30+
31+
📌 **Note:** Deleting a resource group will remove all resources inside it.
32+
33+
---
34+
35+
## **4. Delete Individual Resources (If Needed)**
36+
If you don’t want to delete the entire resource group, follow these steps:
37+
38+
1. Open **Azure Portal** and go to the **Resource groups** section.
39+
2. Click on the specific **resource group**.
40+
3. Select the **resource** you want to delete (e.g., App Service, Storage Account).
41+
4. Click **Delete** at the top.
42+
43+
![Delete Individual Resource](Images/deleteservices.png)
44+
45+
---
46+
47+
## **5. Verify Deletion**
48+
- After a few minutes, refresh the **Resource groups** page.
49+
- Ensure the deleted resource or group no longer appears.
50+
51+
📌 **Tip:** If a resource fails to delete, check if it's **locked** under the **Locks** section and remove the lock.
52+
53+

docs/Images/DeleteRG.png

76.6 KB
Loading

docs/Images/deleteservices.png

116 KB
Loading

docs/Images/resource-groups.png

51.5 KB
Loading

docs/Images/resourcegroup.png

30.4 KB
Loading

0 commit comments

Comments
 (0)