Merge pull request #310847 from ggailey777/UUF-items-jan26

[Functions][UUF] More customer fixes for Jan 2026

Author: prmerger-automator[bot]

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

@@ -122,7 +122,7 @@ builder.Logging.Services.Configure<LoggerFilterOptions>(options =>
     {
         // The Application Insights SDK adds a default logging filter that instructs ILogger to capture only Warning and more severe logs. Application Insights requires an explicit override.
         // Log levels can also be configured using appsettings.json. For more information, see https://learn.microsoft.com/azure/azure-monitor/app/worker-service#ilogger-logs
-        LoggerFilterRule defaultRule = options.Rules.FirstOrDefault(rule => rule.ProviderName
+        LoggerFilterRule? defaultRule = options.Rules.FirstOrDefault(rule => rule.ProviderName
             == "Microsoft.Extensions.Logging.ApplicationInsights.ApplicationInsightsLoggerProvider");
         if (defaultRule is not null)
         {
@@ -828,6 +828,9 @@ public class MyFunction {
 }
 ```
 
+> [!NOTE]
+> When you inject an `ILogger<T>` in your class constructor, like the previous example, the log category is automatically set to the fully qualified name of that class, such as `MyFunctionApp.MyFunction`. These category names contain `.` (period) characters. When you host your function app on Linux, you can't use environment variables to override log levels for categories that contain periods. To work around this limitation, you can instead [configure log levels in your code](#managing-log-levels) or in an `appsettings.json` file.
+
 You can also get the logger from a [FunctionContext] object passed to your function. Call the [GetLogger&lt;T&gt;] or [GetLogger] method, passing a string value that is the name for the category in which the logs are written. The category is usually the name of the specific function from which the logs are written. For more information about categories, see the [monitoring article](functions-monitoring.md#log-levels-and-categories).
 
 Use the methods of [`ILogger<T>`][ILogger&lt;T&gt;] and [`ILogger`][ILogger] to write various log levels, such as `LogWarning` or `LogError`. For more information about log levels, see the [monitoring article](functions-monitoring.md#log-levels-and-categories). You can customize the log levels for components added to your code by registering filters:
@@ -1005,7 +1008,7 @@ builder.Services
 
 builder.Logging.Services.Configure<LoggerFilterOptions>(options =>
     {
-        LoggerFilterRule defaultRule = options.Rules.FirstOrDefault(rule => rule.ProviderName
+        LoggerFilterRule? defaultRule = options.Rules.FirstOrDefault(rule => rule.ProviderName
             == "Microsoft.Extensions.Logging.ApplicationInsights.ApplicationInsightsLoggerProvider");
         if (defaultRule is not null)
         {
@@ -1036,7 +1039,7 @@ var host = new HostBuilder()
     {
         logging.Services.Configure<LoggerFilterOptions>(options =>
         {
-            LoggerFilterRule defaultRule = options.Rules.FirstOrDefault(rule => rule.ProviderName
+            LoggerFilterRule? defaultRule = options.Rules.FirstOrDefault(rule => rule.ProviderName
                 == "Microsoft.Extensions.Logging.ApplicationInsights.ApplicationInsightsLoggerProvider");
             if (defaultRule is not null)
             {

articles/azure-functions/functions-best-practices.md

@@ -2,7 +2,7 @@
 title: Azure Functions best practices
 description: Learn best practices for designing, deploying, and maintaining efficient function code running in Azure.
 ms.assetid: 9058fb2f-8a93-4036-a921-97a0772f503c
-ms.topic: conceptual
+ms.topic: concept-article
 ms.date: 01/20/2026
 ms.devlang: csharp
 ms.custom:

articles/azure-functions/functions-bindings-http-webhook-trigger.md

@@ -706,7 +706,7 @@ You can customize this route using the optional `route` property on the HTTP tri
 
 #### [Isolated worker model](#tab/isolated-process)
 
-The following function code accepts two parameters `category` and `id` in the route and writes a response using both parameters.
+The following function code accepts two parameters `category` and `id` in the route and writes a response using both parameters. The first piece of the variable is the name, and the second is a [route constraint](/aspnet/core/fundamentals/routing#route-constraints).
 
 ```csharp
 [Function("HttpTrigger1")]

articles/azure-functions/functions-bindings-storage-blob-trigger.md

@@ -71,12 +71,33 @@ For more information about the `BlobTrigger` attribute, see [Attributes](#attrib
 
 This function uses a byte array to write a log when a blob is added or updated in the `myblob` container.
 
+Polling-based:
+
+The following example uses the default polling trigger:
+
+```java
+@FunctionName("blobprocessor")
+public void run(
+  @BlobTrigger(name = "file",
+               dataType = "binary",
+               path = "myblob/{name}",
+               connection = "MyStorageAccountAppSetting") byte[] content,
+  @BindingName("name") String filename,
+  final ExecutionContext context
+) {
+  context.getLogger().info("Name: " + filename + " Size: " + content.length + " bytes");
+}
+```
+
+The following example uses an Event Grid trigger:
+
 ```java
 @FunctionName("blobprocessor")
 public void run(
   @BlobTrigger(name = "file",
                dataType = "binary",
                path = "myblob/{name}",
+               source = "EventGrid",
                connection = "MyStorageAccountAppSetting") byte[] content,
   @BindingName("name") String filename,
   final ExecutionContext context

articles/azure-functions/functions-core-tools-reference.md

@@ -278,7 +278,7 @@ The following publish options apply, based on version:
 |**`--list-ignored-files`** | Displays a list of files that are ignored during publishing, which is based on the `.funcignore` file. |
 | **`--list-included-files`** | Displays a list of files that are published, which is based on the `.funcignore` file. |
 | **`--no-build`** | Project isn't built during publishing. For Python, `pip install` isn't performed. |
-| **`--nozip`** | Turns the default `Run-From-Package` mode off. |
+| **`--nozip`** | Turns the default `Run-From-Package` mode off. Files are extracted to the `wwwroot` folder on the server instead of running directly from the deployment package. |
 | **`--overwrite-settings -y`** | Suppress the prompt to overwrite app settings when `--publish-local-settings -i` is used.|
 | **`--publish-local-settings -i`** |  Publish settings in local.settings.json to Azure, prompting to overwrite if the setting already exists. If you're using a [local storage emulator](functions-develop-local.md#local-storage-emulator), first change the app setting to an [actual storage connection](#func-azure-storage-fetch-connection-string). |
 | **`--publish-settings-only`**, **`-o`** |  Only publish settings and skip the content. Default is prompt. |