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
* feat: add support for custom resource group name and refactor resource group references
- Introduced a variable for custom resource group name to allow users to specify an existing resource group.
- Updated resource group references across multiple Terraform files to use the new variable.
- Added documentation for custom resource group usage.
* feat: restore custom resource group documentation
* fix: update documentation for resource group naming and permissions
Copy file name to clipboardExpand all lines: README.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,9 +75,9 @@ This architecture ensures that sensitive enterprise data never traverses public
75
75
-[**Copilot in Power Apps**](https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/ai-overview?WT.mc_id=ppac_inproduct_settings): Enable this setting to allow AI-powered assistance within Power Apps development
76
76
-[**Publish Copilots with AI features**](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance): Allow Copilot authors to publish from Copilot Studio when AI features are enabled
77
77
-**Power Platform licenses**. The designated user must have the following Power Platform licenses assigned:
78
-
-**Microsoft Power Apps**
79
-
-**Power Automate**
80
-
-**Copilot Studio**
78
+
-**Microsoft Power Apps**
79
+
-**Power Automate**
80
+
-**Copilot Studio**
81
81
82
82
To simplify license management, you can use an Azure subscription with a Billing Policy instead of assigning licenses directly. Configure this by using the following flag:
83
83
@@ -257,9 +257,8 @@ telemetry, simply remove `partner_id`. When enabled, the `partner_id` is appende
257
257
258
258
## Responsible AI
259
259
260
-
Microsoft encourages customers to review its Responsible AI Standard when developing AI-enabled
261
-
systems to ensure ethical, safe, and inclusive AI practices. Learn more at
Copy file name to clipboardExpand all lines: docs/app_registration_setup.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,9 @@ will be created:
23
23
- *Contributor*: Grants permission to create and manage Azure resources.
24
24
- *Role Based Access Control Administrator*: Grants permission to assign RBAC roles, which is
25
25
required when using managed identities.
26
+
- *User Access Administrator*: Grants the ability to manage user access to resources, including assigning and revoking permissions.
27
+
28
+
**Note**: You can specify those permissions on a resource group level to limit their scope. See [providing your own resource group documentation](./custom_resource_group.md) for more details.
26
29
27
30
1. Grant **admin consent**forall delegated permissions assigned to the app. This can be donein the [Azure portal](portal.azure.com) under **App registrations**>**API permissions**>**Grant admin consent**.
This template creates a resource group with a randomly generated name by default. You can override this behavior by specifying pre-created resource group during deployment.
4
+
5
+
## Required Variables
6
+
7
+
To use your own resource group, set the following environment variable:
8
+
9
+
```shell
10
+
azd env set RESOURCE_GROUP_NAME "<your-resource-group-name>"
0 commit comments