Teams importing their first estate into Arctic Parade
Prepare an Azure inventory CSV for lifecycle review
Build a useful, minimal inventory export with stable resource IDs, tenant context and enough detail to investigate lifecycle notices.
Published by Arctic Parade LTD · Updated 2026-09-17 · Sources and editorial process
Choose a clear customer boundary
Use the Customer column for the customer or business unit that owns the resource. Keep the naming consistent between uploads. For an internal IT team, a customer label can represent a business unit; use Resource_ID to distinguish resources across subscriptions. Do not encode a password, access token or connection string in any inventory field.
Include only the fields needed for review
Customer and Technology are required. Vendor identifies the publisher. Version is useful when you know the relevant runtime or component version. Resource is a readable label, Resource_ID is the stable identifier, and Environment distinguishes production from test. Keep the file UTF-8 and below the current 2 MB request limit.
Use the resource identifier for repeat imports
The importer updates a resource with the same Resource_ID within the same customer. Without that stable ID, a later upload can create another inventory row. Check both the customer label and resource identifier before importing a revised export. Re-importing is not a deletion instruction; removing a row from a CSV does not delete the existing record.
Do not confuse service and dependency versions
An App Service can host different language runtimes. A storage account version field cannot, by itself, prove which BlobFuse client a server uses. Keep application or host evidence separately when the retirement concerns a dependency rather than the Azure service. Current catalogue matches are review candidates, not configuration attestation.
Try a small export first
Start with a few anonymised resources, check the imported customer and resource counts, and inspect the review queue. Unknown technology names remain private to your workspace and may produce no candidates until a supported catalogue mapping exists. Read the coverage page before treating scan results as a complete risk assessment.
Sources and further reading
Related field guides
Put the process to work.
Explore the current Azure retirement catalogue, then try a small estate scan. Read the coverage limits before acting on a match.