5-acs-report-generate

When to use this skill

Use this skill to export the complete ACS impact assessment to shareable formats.

Examples:

• "Export the ACS assessment to CSV"
• "Generate an ACS deprecation report"
• "Create a summary of ACS migration impact for my team"
• "Save the ACS scan results"

Preconditions

• ACS impact analysis complete (use 4-acs-impact-analyze — recommended)
• OR at minimum: ACS resources scanned + channel detection complete
• Session state contains ACS resource inventory with analysis data

Default File Naming

ACS_ResourceExplorer_{Fast|Full}_v{ToolVersion}_{UtcTimestamp}.{extension}

Examples:
  ACS_ResourceExplorer_Fast_v{ToolVersion}_20260923065155.csv
  ACS_ResourceExplorer_Full_v{ToolVersion}_20260923065155.md
  ACS_ResourceExplorer_Full_v{ToolVersion}_20260923065155.json

Filename components:

• Fast — resource-based channel detection was used
• Full — Azure Monitor metrics-based detection was used
• v — literal version prefix
• ToolVersion — semantic version read from the repository-root VERSION file
• UtcTimestamp — report generation start time in UTC using yyyyMMddHHmmss

Capture the UTC timestamp once at the start of report generation and reuse the same base filename for every selected output format.

Default output location: ./exports/

ACS CSV Columns

Pre-configured CSV structure:

SubscriptionName, SubscriptionId,
ResourceGroup, ResourceName, Location,
LookbackPeriodDays,
EmailDetected, EmailUsageCount,
SMSDetected, SMSUsageCount,
ChatDetected, ChatUsageCount,
CallAutomationDetected, CallAutomationUsageCount,
JobRouterDetected, JobRouterUsageCount,
AdvanceMessagingDetected, AdvanceMessagingUsageCount,
RoomsDetected, RoomsUsageCount,
PhoneNumbersDetected, PhoneNumbersUsageCount,
TotalChannelsImpacted

Workflow

0) Load Knowledge References

Read the repository-root VERSION file before generating the report:

• Trim surrounding whitespace and use the resulting value as ToolVersion
• Require a semantic version in MAJOR.MINOR.PATCH format, optionally with a prerelease or build suffix
• Stop and report an explicit error if the file is missing, unreadable, empty, or contains an invalid version

Read the following knowledge files before generating the report:

• Read docs/knowledge/acs-retirement-dates.md — channel status types and effective dates for report headers
• Read docs/knowledge/acs-migration-paths.md — migration paths and guide links for per-resource recommendations

1) Load ACS Resource Inventory

• Retrieve complete inventory from session state
• Display data availability check:

  ? Report Data Summary:
  ACS Resources: [N]
  Subscriptions Scanned: [N]
  Detection Method: [Resource-based / Metrics-based]
  Impact Analysis: [Complete / Not run]
  Lookback Period: [N] days (if metrics used)
  

• If impact analysis not run: Warn user, continue with available data

2) Configure Report Options

• Ask user: "What report format(s) would you like?"

  1. CSV (Excel-compatible)
  2. Markdown (Human-readable, suitable for sharing)
  3. JSON (Machine-readable, for integration)
  4. All formats
  

• Prompt for output directory (default: ./exports/)
• Determine the scan type from the completed detection method:
  • Resource-based detection: Fast
  • Azure Monitor metrics-based detection: Full
• Generate the filename using: ACS_ResourceExplorer_{Fast|Full}_v{ToolVersion}_{UtcTimestamp}.{extension}
• Capture UtcTimestamp once in UTC using yyyyMMddHHmmss and reuse it for CSV, Markdown, and JSON outputs generated in the same run

3) Create Output Directory

• Check if ./exports/ exists; create if needed
• Verify write permissions

4) Generate CSV Report (if selected)

• Include ALL scanned resources (even those with zero usage — for complete inventory)
• Use the pre-configured channel column structure
• Build CSV content by constructing a header row followed by one data row per resource, with all values comma-separated and quoted where necessary
• Write the CSV content directly to the output file using the Write tool
• Display: "✅ CSV saved: [Path] ([N] resources)"

5) Generate Markdown Report (if selected)

ACS-Specific Markdown Structure:

# ACS Deprecation Impact Assessment Report

**Analysis Date:** [Date]
**Detection Method:** [Resource-based / Azure Monitor Metrics]
**Lookback Period:** [N] days (if metrics used)

## Executive Summary
- Total ACS Resources Scanned: [N]
- Resources Using Retiring Services: [M]
- Subscriptions Analyzed: [X]

## ACS Channel Detection Results

| Channel | Resources Impacted | Usage (last [N] days) | Status Type |
|---------|--------------------|-----------------------|-------------|
| Email   | [N] | [Usage count] messages | ? Retirement |
| SMS     | [N] | [Usage count] messages | ? Retirement |
| Chat    | [N] | [Usage count] messages | ? Retirement |
| Call Automation | [N] | [Usage count] operations | ? Breaking Change |
| Job Router | [N] | [Usage count] operations | ? Breaking Change |
| Advance Messaging | [N] | [Usage count] operations | ? Breaking Change |
 | Rooms | [N] | [Usage count] operations | ? Breaking Change |
| Phone Numbers | [N] | [Usage count] operations | ? Retirement |

## Resource Impact Summary

### [Resource Name]
- **Subscription:** [Name]
- **Resource Group:** [Name]
- **Channels Detected:** Email, Chat, Phone Numbers
- **Usage:** Email: 1,250 | Chat: 543 | Phone Numbers: 15
- **Guides:**
  - ? [Email Retirement Guide](https://aka.ms/acs-retirement#acs-email)
  - ? [Chat Retirement Guide](https://aka.ms/acs-retirement#acs-chat)
 - ? [Calling Breaking Change Guide](https://aka.ms/acs-retirement#acs-voicevideo-calling-sdk) *(if Call Automation detected)*

[Repeat for each resource...]

## ACS Channel Guides
- ? Email — Retirement Guide: https://aka.ms/acs-retirement#acs-email
- ? SMS — Retirement Guide: https://aka.ms/acs-retirement#acs-sms
- ? Chat — Retirement Guide: https://aka.ms/acs-retirement#acs-chat
- ? Call Automation — Breaking Change Guide: https://aka.ms/acs-retirement#acs-voicevideo-calling-sdk
- ? Job Router — Guide: https://aka.ms/acs-retirement
- ? Advance Messaging — Guide: https://aka.ms/acs-retirement
 - ? Rooms — Guide: https://aka.ms/acs-retirement
- ☎️ Phone Numbers — Retirement Guide: https://aka.ms/acs-retirement#acs-number-management-direct-offer

## Next Steps
1. Review migration guides for each detected channel
2. Engage ACS support for complex multi-channel migrations
3. Track progress using the exported CSV

## Confidence & Limitations
- **High confidence:** Channels detected via Azure Monitor metrics
- **Limited confidence:** Channels detected via resource existence only (actual usage unknown)
- **Not assessed:** Channels with zero metrics may still be in use if outside lookback period

6) Generate JSON Report (if selected)

• ACS-specific JSON structure:

  {
    "metadata": {
      "analysisDate": "2026-02-25",
      "analysisType": "ACS Deprecation Impact Assessment",
      "detectionMethod": "Azure Monitor Metrics",
      "lookbackPeriodDays": 90,
      "toolVersion": "{ToolVersion}"
    },
    "summary": {
      "totalACSResources": 2,
      "resourcesWithImpact": 1,
      "subscriptionsScanned": 1,
      "channelBreakdown": {
        "email": { "resourcesDetected": 1, "totalUsage": 1250 },
        "sms": { "resourcesDetected": 0, "totalUsage": 0 },
        "chat": { "resourcesDetected": 1, "totalUsage": 543 },
       "callAutomation": { "resourcesDetected": 0, "totalUsage": 0 },
       "jobRouter": { "resourcesDetected": 0, "totalUsage": 0 },
       "advanceMessaging": { "resourcesDetected": 0, "totalUsage": 0 },
       "rooms": { "resourcesDetected": 0, "totalUsage": 0 },
        "phoneNumbers": { "resourcesDetected": 1, "totalUsage": 15 }
      }
    },
    "resources": [...]
  }
  

7) Display Console Summary

Always display regardless of file export:

=== ACS Impact Assessment Report ===
Analysis Date: [Date]

? Scan Summary:
Total ACS Resources: [N]
Resources with Retiring Services in Use: [M]
Subscriptions Scanned: [N]

? Channel Detection Results:
  ? Email:         [N] resource(s) — [Total Usage] messages (Retirement)
  ? SMS:           [N] resource(s) — [Total Usage] messages (Retirement)
  ? Chat:          [N] resource(s) — [Total Usage] messages (Retirement)
  ? Call Automation: [N] resource(s) — [Total Usage] operations (Breaking Change)
  ? Job Router:    [N] resource(s) — [Total Usage] operations (Breaking Change)
  ? Advance Msg:   [N] resource(s) — [Total Usage] operations (Breaking Change)
  ? Rooms:         [N] resource(s) — [Total Usage] operations (Breaking Change)
  ☎️ Phone Numbers: [N] resource(s) — [Total Usage] operations (Retirement)

? Next Steps:
1. Review exported reports in: ./exports/
2. Read the guide for each detected channel
3. Visit https://aka.ms/acs-retirement for complete migration guidance

8) Display Report Access Information

? Reports Generated:
✅ CSV:      ./exports/ACS_ResourceExplorer_Full_v{ToolVersion}_20260923065155.csv
✅ Markdown: ./exports/ACS_ResourceExplorer_Full_v{ToolVersion}_20260923065155.md
✅ JSON:     ./exports/ACS_ResourceExplorer_Full_v{ToolVersion}_20260923065155.json

Output

• CSV file with complete ACS channel data (configured columns)
• Markdown report with ACS migration guide links
• JSON file for automated processing
• Console summary with channel-level statistics

Knowledge References

Authoritative reference data for this skill — update these files when retirement dates or migration paths change:

• Retirement dates: docs/knowledge/acs-retirement-dates.md
• Migration paths & guide links: docs/knowledge/acs-migration-paths.md

ACS Migration Resources

• ? Email: https://aka.ms/acs-retirement#acs-email
• ? SMS: https://aka.ms/acs-retirement#acs-sms
• ? Chat: https://aka.ms/acs-retirement#acs-chat
• ? Call Automation: https://aka.ms/acs-retirement#acs-voicevideo-calling-sdk
• ? Job Router: https://aka.ms/acs-retirement
• ? Advance Messaging: https://aka.ms/acs-retirement
• ? Rooms: https://aka.ms/acs-retirement
• ☎️ Phone Numbers: https://aka.ms/acs-retirement#acs-number-management-direct-offer
• Retirement & Breaking Changes: https://aka.ms/acs-retirement
• Full migration paths reference: docs/knowledge/acs-migration-paths.md

Related Skills

• Use 4-acs-impact-analyze before this skill for complete reports
• This is the final skill in the ACS workflow