Skip to content

Commit 60bcbd0

Browse files
author
Mike Swantek
committed
docs: rename AI Foundry references to Microsoft Foundry
1 parent 17ec603 commit 60bcbd0

8 files changed

Lines changed: 32 additions & 32 deletions

docs/ACCESSING_PRIVATE_RESOURCES.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Once connected to the Jump VM, you can:
3232
- **Azure AI Search**: Manage indexes via Azure Portal
3333
- **Storage Account**: Browse blobs via Azure Portal or Storage Explorer
3434
- **Container Registry**: Push/pull images using Docker CLI
35-
- **AI Foundry**: Manage projects and deployments
35+
- **Microsoft Foundry**: Manage projects and deployments
3636

3737
### 3. Install Tools on Jump VM (Optional)
3838

docs/DeploymentGuide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -236,7 +236,7 @@ Running postprovision hooks
236236
✓ Lakehouse creation (bronze, silver, gold)
237237
✓ Purview registration
238238
✓ OneLake indexing setup
239-
AI Foundry RBAC configuration
239+
Microsoft Foundry RBAC configuration
240240
```
241241

242242
### Step 5: Verify Deployment
@@ -268,7 +268,7 @@ Then follow the [Post Deployment Steps](./post_deployment_steps.md) to validate:
268268
### Connect Foundry to Search Index
269269

270270
1. Navigate to [ai.azure.com](https://ai.azure.com)
271-
2. Open your AI Foundry project
271+
2. Open your Microsoft Foundry project
272272
3. Go to **Playgrounds****Chat**
273273
4. Click **Add your data** → Select your Search index
274274
5. Test with a sample query

docs/PARAMETER_GUIDE.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This guide focuses on configuration concepts for the **AI Landing Zone**.
1818
1. [Basic Parameters](#basic-parameters)
1919
2. [Deployment Toggles](#deployment-toggles)
2020
3. [Network Configuration](#network-configuration)
21-
4. [AI Foundry Configuration](#ai-foundry-configuration)
21+
4. [Microsoft Foundry Configuration](#microsoft-foundry-configuration)
2222
5. [Individual Service Configuration](#individual-service-configuration)
2323
6. [Common Customization Examples](#common-customization-examples)
2424

@@ -293,11 +293,11 @@ param logAnalyticsWorkspaceResourceId = '/subscriptions/<subId>/resourceGroups/<
293293

294294
---
295295

296-
## AI Foundry Configuration
296+
## Microsoft Foundry Configuration
297297

298298
### aiFoundryDefinition
299299

300-
Controls AI Foundry hub/project and model deployments.
300+
Controls Microsoft Foundry account/project and model deployments.
301301

302302
```json
303303
"aiFoundryDefinition": {
@@ -314,7 +314,7 @@ Controls AI Foundry hub/project and model deployments.
314314
### includeAssociatedResources
315315
**Type**: `boolean`
316316
**Default**: `true`
317-
**Description**: Create dedicated AI Search, Cosmos DB, Key Vault, and Storage for AI Foundry.
317+
**Description**: Create dedicated AI Search, Cosmos DB, Key Vault, and Storage for Microsoft Foundry.
318318

319319
Set to `false` if you want to use shared resources.
320320

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Required Roles and Scopes for AI Foundry isolated network template deployment
1+
# Required Roles and Scopes for Microsoft Foundry isolated network template deployment
22
To deploy this code, assign roles with minimal privileges to create and manage necessary Azure resources. Ensure roles are assigned at the appropriate subscription or resource group levels.
33

44
## Role Assignments:
@@ -13,14 +13,14 @@ Be sure these resource providers are registered in your Azure subscription. To r
1313

1414
| **Resource Type** | **Azure Resource Provider** | **Type** | **Description** |
1515
|-------------------|----------------------------|----------|-----------------|
16-
| Application Insights | Microsoft.Insights | /components | An Azure Application Insights instance associated with the Azure AI Foundry Hub |
16+
| Application Insights | Microsoft.Insights | /components | An Azure Application Insights instance associated with the Microsoft Foundry account |
1717
|Azure Log Analytics|Microsoft.OperationalInsights|/workspaces|An Azure Log Analytics workspace used to collect diagnostics|
18-
|Azure Key Vault|Microsoft.KeyVault|/vaults|An Azure Key Vault instance associated with the Azure AI Foundry Hub|
19-
|Azure Storage Account|Microsoft.Storage|/storageAccounts|An Azure Storage instance associated with the Azure AI Foundry Hub|
20-
|Azure Container Registry|Microsoft.ContainerRegistry|/registries|An Azure Container Registry instance associated with the Azure AI Foundry Account|
18+
|Azure Key Vault|Microsoft.KeyVault|/vaults|An Azure Key Vault instance associated with the Microsoft Foundry account|
19+
|Azure Storage Account|Microsoft.Storage|/storageAccounts|An Azure Storage instance associated with the Microsoft Foundry account|
20+
|Azure Container Registry|Microsoft.ContainerRegistry|/registries|An Azure Container Registry instance associated with the Microsoft Foundry account|
2121
|Azure AI Services|Microsoft.CognitiveServices|/accounts|An Azure AI Services as the model-as-a-service endpoint provider including GPT-4o and ADA Text Embeddings model deployments|
22-
|Azure Virtual Network|Microsoft.Network|/virtualNetworks|A bring-your-own (BYO) virtual network hosting a virtual machine to connect to Azure AI Foundry which will be behind a private endpoint when in network isolation mode. |
22+
|Azure Virtual Network|Microsoft.Network|/virtualNetworks|A bring-your-own (BYO) virtual network hosting a virtual machine to connect to Microsoft Foundry which will be behind a private endpoint when in network isolation mode. |
2323
|Bastion Host|Microsoft.Network||A Bastion Host defined in the BYO virtual network that provides RDP connectivity to the jumpbox virtual machine|
2424
|Azure NAT Gateway|Microsoft.Network|/natGateways|An Azure NAT Gateway that provides outbound connectivity to the jumpbox virtual machine|
25-
|Azure Private Endpoints|Microsoft.Network|/privateEndpoints|Azure Private Endpoints defined in the BYO virtual network for Azure Container Registry, Azure Key Vault, Azure Storage Account, and Azure AI Foundry Hub/Project|
25+
|Azure Private Endpoints|Microsoft.Network|/privateEndpoints|Azure Private Endpoints defined in the BYO virtual network for Azure Container Registry, Azure Key Vault, Azure Storage Account, and Microsoft Foundry account/project|
2626
|Azure Private DNS Zones|Microsoft.Network|/privateDnsZones|Azure Private DNS Zones are used for the DNS resolution of the Azure Private Endpoints|

docs/TRANSPARENCY_FAQ.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
### What is the Deploy Your AI Application In Production solution accelerator?
66

7-
This solution accelerator automates the deployment of a complete, production-ready AI application environment in Azure. It provisions Azure AI Foundry, Microsoft Fabric, Azure AI Search, and Microsoft Purview—all pre-wired with private networking, managed identities, and governance controls.
7+
This solution accelerator automates the deployment of a complete, production-ready AI application environment in Azure. It provisions Microsoft Foundry, Microsoft Fabric, Azure AI Search, and Microsoft Purview—all pre-wired with private networking, managed identities, and governance controls.
88

99
### What is the intended use of this solution accelerator?
1010

docs/automation-outputs-mapping.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,11 +39,11 @@ The postprovision automation scripts consume deployment outputs via the `AZURE_O
3939
| `aiSearchSubscriptionId` | `aiSearchSubscriptionId` | OneLake indexing scripts | Subscription for AI Search |
4040
| `aiSearchAdditionalAccessObjectIds` | `aiSearchAdditionalAccessObjectIds` | RBAC scripts | Optional Entra principals granted Search roles |
4141

42-
### AI Foundry
42+
### Microsoft Foundry
4343

4444
| Bicep Output | Script Variable | Used By | Purpose |
4545
|-------------|-----------------|---------|---------|
46-
| `aiFoundryProjectName` | `aiFoundryName` | `06_setup_ai_foundry_search_rbac.ps1` | AI Foundry project name |
46+
| `aiFoundryProjectName` | `aiFoundryName` | `06_setup_ai_foundry_search_rbac.ps1` | Microsoft Foundry project name |
4747
| `aiFoundryServicesName` | `aiServicesName` | RBAC scripts | Cognitive Services account name |
4848

4949
### Purview Integration

docs/deploy_app_from_foundry.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,33 @@
1-
# Deploy an Application from Azure AI Foundry
1+
# Deploy an Application from Microsoft Foundry
22

3-
This guide explains how to deploy a chat application directly from the Azure AI Foundry playground to Azure App Service.
3+
This guide explains how to deploy a chat application directly from the Microsoft Foundry playground to Azure App Service.
44

55
## Overview
66

7-
Azure AI Foundry provides a built-in capability to publish playground experiences as web applications. This accelerator deploys the required infrastructure (App Service, managed identity, networking) so you can publish directly from the Foundry playground.
7+
Microsoft Foundry provides a built-in capability to publish playground experiences as web applications. This accelerator deploys the required infrastructure (App Service, managed identity, networking) so you can publish directly from the Foundry playground.
88

99
## Prerequisites
1010

1111
- Completed deployment of this accelerator (`azd up`)
12-
- Access to the AI Foundry project via the Jump VM
12+
- Access to the Microsoft Foundry project via the Jump VM
1313
- An AI Search index with your data (created via OneLake indexer or manually)
1414

1515
## Steps to Deploy an App from Foundry Playground
1616

17-
### 1. Access AI Foundry via Jump VM
17+
### 1. Access Microsoft Foundry via Jump VM
1818

19-
Since all resources are deployed with private endpoints, you must access AI Foundry through the Jump VM:
19+
Since all resources are deployed with private endpoints, you must access Microsoft Foundry through the Jump VM:
2020

2121
1. Go to the [Azure Portal](https://portal.azure.com)
2222
2. Navigate to your resource group
2323
3. Select the **Jump VM** (Windows Virtual Machine)
2424
4. Click **Connect****Bastion**
2525
5. Enter the VM credentials (set during deployment)
26-
6. Once connected, open a browser and navigate to [AI Foundry](https://ai.azure.com)
26+
6. Once connected, open a browser and navigate to [Microsoft Foundry](https://ai.azure.com)
2727

2828
### 2. Configure Your Playground
2929

30-
1. In AI Foundry, select your **Project**
30+
1. In Microsoft Foundry, select your **Project**
3131
2. Navigate to **Playgrounds****Chat playground**
3232
3. Configure your deployment:
3333
- Select your **GPT model deployment** (e.g., gpt-4o)
@@ -61,7 +61,7 @@ After deployment completes:
6161
## Additional Resources
6262

6363
- [Deploy a web app for chat on your data](https://learn.microsoft.com/en-us/azure/ai-foundry/how-to/deploy-web-app)
64-
- [Azure AI Foundry documentation](https://learn.microsoft.com/en-us/azure/ai-foundry/)
64+
- [Microsoft Foundry documentation](https://learn.microsoft.com/en-us/azure/ai-foundry/)
6565
- [Customize the web app](https://learn.microsoft.com/en-us/azure/ai-foundry/how-to/deploy-web-app#customize-the-web-app)
6666

6767
## Troubleshooting

docs/faq.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
# Frequently Asked Questions
22

3-
## How do Azure AI Foundry account and project identities interact with Azure AI Search RBAC?
3+
## How do Microsoft Foundry account and project identities interact with Azure AI Search RBAC?
44

5-
Fabric/Azure AI Foundry creates **separate managed identities** for the Foundry account and for each project. Azure RBAC permissions do **not** cascade from the account to its projects, so a role assignment that targets the account identity does not automatically grant the same access to the project identity.
5+
Microsoft Foundry creates **separate managed identities** for the Foundry account and for each project. Azure RBAC permissions do **not** cascade from the account to its projects, so a role assignment that targets the account identity does not automatically grant the same access to the project identity.
66

77
The post-provision script `scripts/automationScripts/OneLakeIndex/06_setup_ai_foundry_search_rbac.ps1` therefore resolves **both** identities:
88

9-
- `aiFoundryIdentity` → the AI Foundry **account** managed identity
10-
- `projectPrincipalId` → the AI Foundry **project** managed identity
9+
- `aiFoundryIdentity` → the Microsoft Foundry **account** managed identity
10+
- `projectPrincipalId` → the Microsoft Foundry **project** managed identity
1111

1212
It then assigns the required Azure AI Search roles to every principal it finds. If the script cannot resolve the project identity, it logs a warning and only the account identity receives the roles. In that case, re-run the script once the project identity exists or assign the roles manually.
1313

@@ -46,9 +46,9 @@ az role assignment create \
4646

4747
Because the knowledge source uses the **project** identity when it ingests data, those roles must be granted to the project principal even if the account identity already has them.
4848

49-
## How do I integrate an existing Azure AI Foundry project into the AI Landing Zone?
49+
## How do I integrate an existing Microsoft Foundry project into the AI Landing Zone?
5050

51-
Integrating the new Azure AI Foundry project model (Cognitive Services account plus project announced at Ignite) into an AI Landing Zone is a matter of extending the landing zone controls so the project runs entirely inside the isolated estate. Work through these considerations:
51+
Integrating the Microsoft Foundry project model (Cognitive Services account plus project) into an AI Landing Zone is a matter of extending the landing zone controls so the project runs entirely inside the isolated estate. Work through these considerations:
5252

5353
1. **Locate the project**: Record the account and project resource IDs, region, and tenant. Confirm the region aligns with the landing zone virtual network and private DNS footprint so private endpoints can be created without cross-region limitations.
5454
2. **Carve out network space**: Add a dedicated subnet (or set of subnets) in the landing zone virtual network for the Foundry managed network. Apply the landing zone NSG, UDR, and firewall baselines. If the project already uses managed network isolation, update it to target the new subnet; otherwise plan for a fresh isolated project and migrate assets with export/import tooling.

0 commit comments

Comments
 (0)