.NET: Update Microsoft Foundry branding#6999
Open
nicholasdbrady wants to merge 1 commit into
Open
Conversation
Replace user-facing Azure AI Foundry branding with Microsoft Foundry across docs, samples, comments, and display text while preserving technical identifiers. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
Contributor
There was a problem hiding this comment.
Pull request overview
Updates user-facing references from Azure AI Foundry to Microsoft Foundry across the repository to reflect current branding, while intentionally preserving technical identifiers (namespaces, package names, env vars, URLs).
Changes:
- Replaces “Azure AI Foundry” with “Microsoft Foundry” in docs/ADRs, sample READMEs, and inline comments across Python and .NET.
- Updates sample configuration/help text (env var descriptions, prompts, UI strings) to use the new brand.
- Refreshes a few .NET test/sample strings so prompts and skip reasons align with the new terminology.
Reviewed changes
Copilot reviewed 224 out of 224 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| TRANSPARENCY_FAQ.md | Updates provider/portal branding in Responsible AI transparency FAQ text. |
| python/samples/SAMPLE_GUIDELINES.md | Updates sample guidance and env var descriptions to Microsoft Foundry terminology. |
| python/packages/azure-contentunderstanding/agent_framework_azure_contentunderstanding/_context_provider.py | Updates docstrings for service endpoint branding (needs correction to CU endpoint wording). |
| python/packages/declarative/agent_framework_declarative/_workflows/_executors_agents.py | Updates docstring branding for declarative executor (should acknowledge retained InvokeAzureAgent naming). |
| dotnet/src/Shared/Samples/TestConfiguration.cs | Updates XML docstrings mentioning Foundry endpoint wording (minor grammar fix suggested). |
eavanvalkenburg
approved these changes
Jul 9, 2026
rogerbarreto
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation & Context
Microsoft renamed
Azure AI FoundrytoMicrosoft Foundryas part of a product branding update. The repository still contained references to the old name across documentation, code comments, sample READMEs, and display strings. This PR updates those user-facing references so contributors and users see the current product brand consistently.Description & Review Guide
Azure AI Foundryreferences withMicrosoft Foundryacross 224 files, including ADRs, Python and .NET sample READMEs, comments, display strings, CI workflow comments, and inline documentation. Technical identifiers such as package names, namespaces, API types, environment variables, and URLs are preserved.Related Issue
No dedicated issue was filed for this trivial documentation and display-string branding update. A search of open issues and pull requests found no existing tracking item for this exact rename.
Contribution Checklist
breaking changelabel (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.