Skip to content

Commit d241a37

Browse files
committed
fixing links
1 parent f4c0e54 commit d241a37

File tree

6 files changed

+8
-8
lines changed

6 files changed

+8
-8
lines changed

articles/ai-foundry/concepts/concept-model-distillation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,6 @@ We used an advanced prompt during synthetic data generation. The advanced prompt
4141

4242
## Related content
4343

44-
- [What is Azure AI Foundry?](../what-is-ai-studio.md)
44+
- [What is Azure AI Foundry?](../what-is-ai-foundry.md)
4545
- [Deploy Meta Llama 3.1 models with Azure AI Foundry](../how-to/deploy-models-llama.md)
4646
- [Azure AI Foundry FAQ](../faq.yml)

articles/ai-foundry/concepts/concept-synthetic-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,6 @@ To see how to generate synthetic data, you can use the [sample notebook](https:/
3535

3636
## Related content
3737

38-
- [What is Azure AI Foundry?](../what-is-ai-studio.md)
38+
- [What is Azure AI Foundry?](../what-is-ai-foundry.md)
3939
- [Deploy Meta Llama 3.1 models with Azure AI Foundry](../how-to/deploy-models-llama.md)
4040
- [Azure AI Foundry FAQ](../faq.yml)

articles/ai-foundry/concepts/connections.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ When you create a connection with an existing Azure storage account, you can cho
5454
- **Identity-based**: Use your Microsoft Entra ID or managed identity to authenticate data access.
5555

5656
> [!TIP]
57-
> When using an identity-based connection, Azure role-based access control (Azure RBAC) is used to determine who can access the connection. You must assign the correct Azure RBAC roles to your developers before they can use the connection. For more information, see [Scenario: Connections using Microsoft Entra ID](rbac-ai-studio.md#scenario-connections-using-microsoft-entra-id-authentication).
57+
> When using an identity-based connection, Azure role-based access control (Azure RBAC) is used to determine who can access the connection. You must assign the correct Azure RBAC roles to your developers before they can use the connection. For more information, see [Scenario: Connections using Microsoft Entra ID](rbac-ai-foundry.md#scenario-connections-using-microsoft-entra-id-authentication).
5858
5959

6060
The following table shows the supported Azure cloud-based storage services and authentication methods:
@@ -84,7 +84,7 @@ A Uniform Resource Identifier (URI) represents a storage location on your local
8484

8585
Connections allow you to securely store credentials, authenticate access, and consume data and information. Secrets associated with connections are securely persisted in the corresponding Azure Key Vault, adhering to robust security and compliance standards. As an administrator, you can audit both shared and project-scoped connections on a hub level (link to connection rbac).
8686

87-
Azure connections serve as key vault proxies, and interactions with connections are direct interactions with an Azure key vault. Azure AI Foundry connections store API keys securely, as secrets, in a key vault. The key vault [Azure role-based access control (Azure RBAC)](./rbac-ai-studio.md) controls access to these connection resources. A connection references the credentials from the key vault storage location for further use. You won't need to directly deal with the credentials after they're stored in the hub's key vault. You have the option to store the credentials in the YAML file. A CLI command or SDK can override them. We recommend that you avoid credential storage in a YAML file, because a security breach could lead to a credential leak.
87+
Azure connections serve as key vault proxies, and interactions with connections are direct interactions with an Azure key vault. Azure AI Foundry connections store API keys securely, as secrets, in a key vault. The key vault [Azure role-based access control (Azure RBAC)](./rbac-ai-foundry.md) controls access to these connection resources. A connection references the credentials from the key vault storage location for further use. You won't need to directly deal with the credentials after they're stored in the hub's key vault. You have the option to store the credentials in the YAML file. A CLI command or SDK can override them. We recommend that you avoid credential storage in a YAML file, because a security breach could lead to a credential leak.
8888

8989

9090
## Next steps

articles/ai-foundry/concepts/management-center.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,10 +40,10 @@ Assign roles, manage users, and ensure that all settings comply with organizatio
4040

4141
:::image type="content" source="../media/management-center/user-management.png" alt-text="Screenshot of the user management section of the management center." lightbox="../media/management-center/user-management.png":::
4242

43-
For more information, see [Role-based access control](rbac-ai-studio.md#assigning-roles-in-azure-ai-foundry-portal).
43+
For more information, see [Role-based access control](rbac-ai-foundry.md#assigning-roles-in-azure-ai-foundry-portal).
4444

4545
## Related content
4646

4747
- [Security baseline](/security/benchmark/azure/baselines/azure-ai-studio-security-baseline)
4848
- [Built-in policy to allow specific models](../how-to/built-in-policy-model-deployment.md)
49-
- [Custom policy to allow specific models](../how-to/custom-policy-model-deployment.md)
49+
- [Custom policy to allow specific models](../model-inference/how-to/configure-deployment-policies.md)

articles/ai-services/openai/how-to/use-blocklists.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -253,7 +253,7 @@ If the completion itself is blocked, the response returns `200`, as the completi
253253

254254
#### [Azure AI Foundry](#tab/foundry)
255255

256-
[!INCLUDE [use-blocklists](../../../ai-studio/includes/use-blocklists.md)]
256+
[!INCLUDE [use-blocklists](../../../ai-foundry/includes/use-blocklists.md)]
257257

258258
---
259259

articles/machine-learning/concept-endpoint-serverless-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Certain models in the model catalog can be deployed as a serverless API with pay
2727

2828
Pay-as-you-go billing is available only to users whose Azure subscription belongs to a billing account in a country/region where the model provider has made the offer available (see "offer availability region" in the table in the next section). If the offer is available in the relevant region, the user then must have a Hub/Project in the Azure region where the model is available for deployment or fine-tuning, as applicable (see "Hub/Project Region" columns in the following tables).
2929

30-
[!INCLUDE [region-availability-maas](../ai-studio/includes/region-availability-maas.md)]
30+
[!INCLUDE [region-availability-maas](../ai-foundry/includes/region-availability-maas.md)]
3131

3232

3333
## Alternatives to region availability

0 commit comments

Comments
 (0)