Logging in Azure Functions running in an Isolated Worker process

[springcomp]

This PR adds a warning about log category names with a . character when running on Linux App Service plans.

There, logs with a category name that contains a . (period) character cannot be easily overridden using environment variable.
Although this is somewhat documented in the Logging in C# document, I think it would be worthwhile to add a short mention of those limitations here.

[prmerger-automator]

@springcomp : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 62246c7:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/azure-functions/dotnet-isolated-process-guide.md	⚠️Warning		Details

articles/azure-functions/dotnet-isolated-process-guide.md

• Line 814, Column 3: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=bash#set-log-level-by-command-line-environment-variables-and-other-configuration' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 814, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=bash#set-log-level-by-command-line-environment-variables-and-other-configuration' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[v-dirichards]

@ggailey777

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[learn-build-service-prod]

Learn Build status updates of commit ea3c0ec:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/azure-functions/dotnet-isolated-process-guide.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[springcomp]

#sign-off

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @ggailey777

[learn-build-service-prod]

Learn Build status updates of commit dfeff3b:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/azure-functions/dotnet-isolated-process-guide.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[v-ccolin]

I sent an email to the content owner on 01/12/2025.

@MicrosoftDocs/public-repo-pr-review-team