Skip to content

Commit a5b7166

Browse files
committed
fix link
1 parent debbc87 commit a5b7166

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/azure-developer-cli/resource-group-scoped-deployments.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
---
22
title: Resource Group Scoped Deployments
33
description: How to deploy templates that target resource group scope instead of subscription scope with the Azure Developer CLI (azd)
4-
author: gkulin
5-
ms.author: gracekulin
64
ms.date: 09/12/2024
75
ms.service: azure-dev-cli
86
ms.topic: article
@@ -55,7 +53,7 @@ In this article, you learn how to modify templates to enable resource group scop
5553
> [!NOTE]
5654
> For an example of these changes applied to the [React Web App with Node.js API and MongoDB on Azure template](https://github.com/Azure-Samples/todo-nodejs-mongo), see [this GitHub comparison](https://github.com/Azure-Samples/todo-nodejs-mongo/compare/main...ellismg:todo-nodejs-mongo:ellismg/move-to-rg-scope).
5755
58-
To set the resource group to deploy to manually, you can set `AZURE_RESOURCE_GROUP` in your environment. Learn more about that [here](./manage-environment-variables.md#user-provided-environment-variables).
56+
To set the resource group to deploy to manually, you can set `AZURE_RESOURCE_GROUP` in your [environment variables](./manage-environment-variables.md).
5957
6058
Alternatively, if you do not have a resource group specified in your environment, `azd` prompts you to pick an existing resource group from your subscription or create a new one when you run `azd provision`.
6159

0 commit comments

Comments
 (0)