The Azure Storage emulator endpoints in Azure Functions projects were showing generic names ("blob", "queue", "table") in the dashboard, causing confusion when users clicked on them and received different API responses. This PR adds descriptive display names to make it clear what each endpoint represents.

Problem

When creating Azure Functions projects with Aspire orchestration, the default storage resource creates three endpoints:

• blob endpoint on port 10000
• queue endpoint on port 10001
• table endpoint on port 10002

These endpoints all appeared with generic names in the dashboard, but when users clicked on them, they would get different responses:

• Some returned XML API responses
• Others showed "page not working" errors

This inconsistency was confusing because all endpoints appeared to be from the same "functionstorage" resource.

Solution

Added descriptive display names using the WithUrlForEndpoint method:

builder.WithHttpEndpoint(name: "blob", targetPort: 10000)
       .WithHttpEndpoint(name: "queue", targetPort: 10001)
       .WithHttpEndpoint(name: "table", targetPort: 10002)
       .WithUrlForEndpoint("blob", url => url.DisplayText = "Blob Service API")
       .WithUrlForEndpoint("queue", url => url.DisplayText = "Queue Service API") 
       .WithUrlForEndpoint("table", url => url.DisplayText = "Table Service API")

Impact

• Users will now see clearly labeled endpoints: "Blob Service API", "Queue Service API", "Table Service API"
• This eliminates confusion about what each endpoint does
• The underlying functionality remains unchanged - only the display names are improved
• No breaking changes to existing APIs or workflows

The solution follows the established pattern in Aspire where WithUrlForEndpoint is used to customize how endpoints appear in the dashboard.

Fixes #10416.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.