Conversation
dotnet-policy-service
bot
added
the
community-contribution
There was a problem hiding this comment.
Pull request overview
Updates AI documentation to align terminology with the ongoing Foundry branding changes across the .NET AI docs.
Changes:
- Adjusts capitalization/wording for “Foundry tools” references in AI ecosystem and authentication docs.
- Updates wording around Azure AI services vs. Foundry tools in the ecosystem overview.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| docs/ai/dotnet-ai-ecosystem.md | Tweaks Foundry-related wording in the SDK ecosystem overview and the “Foundry Tools” SDK section. |
| docs/ai/azure-ai-services-authentication.md | Updates Foundry-related terminology in the authentication/authorization conceptual article. |
You can also share your feedback on Copilot code review. Take the survey.
| ## Authentication using Microsoft Entra ID | ||
|
|
||
| Microsoft Entra ID is a cloud-based identity and access management service that provides a vast set of features for different business and app scenarios. Microsoft Entra ID is the recommended solution to connect to Azure OpenAI and other Foundry Tools and provides the following benefits: | ||
| Microsoft Entra ID is a cloud-based identity and access management service that provides a vast set of features for different business and app scenarios. Microsoft Entra ID is the recommended solution to connect to Azure OpenAI and other Foundry tools and provides the following benefits: |
There was a problem hiding this comment.
The preceding section links to Microsoft Entra ID using a root-relative fragment (/#...). Use a valid link target (for example, an in-page anchor for this article’s Entra section) so readers aren’t sent to the site root / a non-existent anchor.
docs/ai/dotnet-ai-ecosystem.md
Outdated
| ### .NET SDKs for Foundry Tools | ||
|
|
||
| Azure offers many other Foundry Tools to build specific application capabilities and workflows. Most of these services provide a .NET SDK to integrate their functionality into custom apps. Some of the most commonly used services are shown in the following table. For a complete list of available services and learning resources, see the [Foundry Tools](/azure/ai-services/what-are-ai-services) documentation. | ||
| Azure offers many other AI services to build specific application capabilities and workflows. Most of these services provide a .NET SDK to integrate their functionality into custom apps. Some of the most commonly used services are shown in the following table. For a complete list of available services and learning resources, see the [Foundry Tools](/azure/ai-services/what-are-ai-services) documentation. |
There was a problem hiding this comment.
This paragraph now says “Azure offers many other AI services…”, but the link text and section heading still refer to “Foundry Tools”. Either keep the terminology consistent (Foundry tools throughout) or update the link text/section header to match “AI services” so readers don’t think these are different concepts.
There was a problem hiding this comment.
Before PR 51841 was merged, line 60 said, "Azure offers many other AI services ..." Commit ac15642 adds a phrase to tie this section into the general discussion of AI services in the rest of the article.
|
|
||
| Application requests to Foundry Tools must be authenticated. In this article, you explore the options available to authenticate to Azure OpenAI and other Foundry Tools using .NET. Most Foundry Tools offer two primary ways to authenticate apps and users: | ||
| Application requests to Microsoft Foundry tools must be authenticated. In this article, you explore the options available to authenticate to Azure OpenAI and other Foundry tools using .NET. Most Foundry tools offer two primary ways to authenticate apps and users: | ||
|
|
There was a problem hiding this comment.
The naming is inconsistent in the opening: it uses “Microsoft Foundry tools” here, but the rest of the article uses “Foundry tools” / “Foundry tool”. Pick one product name and use it consistently throughout the article to avoid confusing readers (and to align with the branding change this PR targets).
There was a problem hiding this comment.
The first mention needs to be "Microsoft Foundry." Later mentions use just "Foundry."
| @@ -6,9 +6,9 @@ ms.topic: concept-article | |||
| ms.date: 04/09/2025 | |||
There was a problem hiding this comment.
ms.date doesn’t reflect this update. Since this article’s content changed, update ms.date to the date of this change so the page metadata stays accurate.
| ms.date: 04/09/2025 | |
| ms.date: 03/06/2026 |
| ### Authenticate to Azure locally | ||
|
|
||
| When developing apps locally that connect to Foundry Tools, authenticate to Azure using a tool such as Visual Studio or the Azure CLI. Your local credentials can be discovered by the `Azure.Identity` client library and used to authenticate your app to Azure services, as described in the [Configure the app code](/#configure-your-app-code) section. | ||
| When developing apps locally that connect to Foundry tools, authenticate to Azure using a tool such as Visual Studio or the Azure CLI. Your local credentials can be discovered by the `Azure.Identity` client library and used to authenticate your app to Azure services, as described in the [Configure the app code](/#configure-your-app-code) section. |
There was a problem hiding this comment.
The link to “Configure the app code” uses /#configure-your-app-code, which points to the site root with a fragment and doesn’t match this article’s heading text. Change it to a valid in-page anchor for this article (or a correct external URL) to avoid a broken link.
| When developing apps locally that connect to Foundry tools, authenticate to Azure using a tool such as Visual Studio or the Azure CLI. Your local credentials can be discovered by the `Azure.Identity` client library and used to authenticate your app to Azure services, as described in the [Configure the app code](/#configure-your-app-code) section. | |
| When developing apps locally that connect to Foundry tools, authenticate to Azure using a tool such as Visual Studio or the Azure CLI. Your local credentials can be discovered by the `Azure.Identity` client library and used to authenticate your app to Azure services, as described in the [Configure the app code](#configure-the-app-code) section. |
|
@gewarren: Your comment in PR 51841 questioning the use of "Foundry Tool" was spot on. The term "Foundry Tool" was incorrectly listed in the rebranding sheet. I'm now making some adjustments to branding edits to change the capitalization of "Foundry Tool" and "Foundry Tools" when those terms are used generically, not as part of a product name. For this PR, I'm happy to make whatever edits are needed to make the articles accurate and the formatting consistent. Question for you: This PR changes the H1 of Foundry Tools authentication and authorization using .NET to "# Foundry tools authentication and authorization using .NET" (with "Tools" switched to "tools"), because the article focuses on connections to Azure OpenAI, which is part of Microsoft Foundry, not Foundry Tools. If you're okay with this change to the H1, should I also update the capitalization in the following references to that article, which currently use |
Summary
This PR updates content to support branding changes in Foundry.
For details about this effort, contact Nitin Mehrotra, McLean Schofield, or Renee Wesberry.
ADO request: 543990
Internal previews