Add how-to doc for customizing ARM long-running operation headers

[Copilot]

• Explore repo structure, existing docs format, and ARM LRO templates
• Create how-to document for customizing ARM LROs at website/src/content/docs/docs/howtos/ARM/long-running-operations.md
  • Introduction explaining LRO header customization via LroHeaders template parameter
  • LRO Header Types reference table
  • Section for PUT (CreateOrUpdate) operations — default, Location header, both headers
  • Section for PATCH (Update) operations — default, Azure-AsyncOperation header, both headers
  • Section for DELETE operations — default, Azure-AsyncOperation header, both headers (FinalResult = void)
  • Section for POST (Resource Action) operations — with response and no-content variants
  • Each section shows default headers and how to customize while retaining correct FinalResult
• Format the document with prettier
• Simplify ArmLroLocationHeader and ArmAsyncOperationHeader usages to use named FinalResult parameter with template defaults
• Fix intro text: LRO headers appear in 201 Created for PUT and 202 Accepted for PATCH/DELETE/POST
• Simplify ArmCombinedLroHeaders usages to use named FinalResult parameter with template defaults
• Run pnpm format on all changed markdown files
• Run code review — no issues found
• Run CodeQL checker — no code changes to analyze

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[markcowl]

@copilot You can simplify the usage of ArmLroLocationHeader and ArmAsyncOperationHeader templates by taking the template defaultsand providing the FinalResult value explicitly. For example, ArmLroLocationHeader<FinalResult = MyResource>

[Copilot]

@copilot You can simplify the usage of ArmLroLocationHeader and ArmAsyncOperationHeader templates by taking the template defaultsand providing the FinalResult value explicitly. For example, `ArmLroLo...

Simplified all ArmLroLocationHeader and ArmAsyncOperationHeader usages to rely on template defaults and only specify FinalResult explicitly (e.g., ArmLroLocationHeader<FinalResult = MyResource>). Commit: 46ce5cf

[markcowl]

@copilot. It is not strctly true that LroHeaders changes only the headers in 202 response for all operation types [although this is always true for delete and POST operations] (for example, it changes the headers in the 201 response to PUT operations)

[Copilot]

@copilot. It is not strctly true that LroHeaders changes only the headers in 202 response for all operation types [although this is always true for delete and POST operations] (for example, it change...

Fixed the intro to clarify that LRO headers appear in the 201 Created response for PUT operations and in the 202 Accepted response for PATCH, DELETE, and POST operations. Commit: accd7f9

[azure-sdk]

No changes needing a change description found.

[markcowl]

@copilot You can similarly simplify the usage of ArmCombinedLroHeaders to simply use the FinalResult parameter explicitly.

[Copilot]

@copilot You can similarly simplify the usage of ArmCombinedLroHeaders to simply use the FinalResult parameter explicitly.

Simplified all ArmCombinedLroHeaders usages to use the named FinalResult parameter (e.g., ArmCombinedLroHeaders<FinalResult = MyResource> instead of ArmCombinedLroHeaders<ArmOperationStatus, MyResource>). Commit: 03c78f8

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website

[markcowl]

@copilot please run pnpm format over all changed markdown files in this pr

[Copilot]

@copilot please run pnpm format over all changed markdown files in this pr

Ran pnpm format on the changed markdown file. Prettier adjusted line wrapping in two code blocks. Commit: 4d3f3b0