Migrate Azure Reserved Instances and Azure Savings Plans to Recon-Based Subscriptions in Work 365

Modified on Fri, May 1 at 1:56 PM

Short Summary

Work 365’s current Reserved Instance and Savings Plans billing model is reconciliation-driven, with billing based on Microsoft reconciliation data rather than the older license-based pattern. Older Azure Reserved Instance (ARI) and Azure Savings Plan (ASP) records that were originally created as license-based subscriptions should be migrated carefully so future syncs do not keep treating those legacy records as the active provider-backed subscriptions. The exact version threshold and cleanup sequence below are based on the migration procedure you provided.

Applies To

Work 365 environments where existing ARI or ASP records were originally created as license-based subscriptions and now need to be aligned to the current Recon-based billing model. Public Work 365 documentation supports the current-state model for Reserved Instances through its reconciliation-driven billing guidance, while older Work 365 documentation shows Reserved Instances historically syncing as license-based subscriptions. The specific environment threshold of DV 5.2.x.y or later or PV 3.2.x.y or later comes from your uploaded migration procedure.

Prerequisites

Before you begin, confirm the environment is already on the supported version noted in your migration procedure and that the person performing the work can create views, export and update records in Excel Online, update subscriptions, update License Change Logs, and delete Scheduled License Change Logs. Your procedure also recommends exporting any Scheduled License Change Logs you may need to recreate later.

If you plan to edit records through Excel Online, Microsoft documents that model-driven app data can be opened in Excel Online and edited there, with the recommendation to preserve the existing workbook structure and formatting so save-back works correctly. For large cleanup batches, Microsoft documents bulk deletion in the Power Platform admin center as the supported option for targeted large-volume deletes and separately documents how to review and manage bulk deletion jobs afterward.

This migration should be treated as a billing-data cleanup, not just a display cleanup. Work 365 documents that subscriptions are tied to invoicing through the Billing Contract, and that License Change Logs are critical to the invoicing process and represent the lifecycle history of a subscription.

Procedure / Solution Steps

1. Create a License Change Logs view for Azure Reserved Instances and Azure Savings Plans

Create a License Change Logs view named ARIs & ASPs and use these filters with OR logic:

Provider Part Number begins with DZH318Z09V6F for Azure Savings Plans
Family equals NCE:RESERVEDINSTANCE for Azure Reserved Instances
Purchase Type equals MicrosoftCsp:ReservedInstance for Azure Reserved Instances

Add these columns:

Customer
Billing Contract
Subscription Name
Billing Type
Family
Purchase Type
Subscription ID
Provider Properties
Provider
Provider Account
External Description
Status
Status Reason

Then save the view and confirm that all expected ARI and ASP subscriptions appear. If records are missing, review the Family, Provider Part Number, and Purchase Type values on the source records. These filters and columns come from your migration procedure.

2. Deactivate the existing license-based subscriptions

From the ARIs & ASPs view, export the records to Excel Online. Update only these columns:

Provider = Do Nothing Provider
Provider Account = clear the value
Provider Properties = clear the value
Status = Inactive
Status Reason = Inactive
External Description = Deactivation due to Recon migration
Subscription ID = add the prefix old- to the current value

Example:
39c36c18-227c-4546-9a42-d69125a29c16 → old-39c36c18-227c-4546-9a42-d69125a29c16

This step is part of your migration procedure and is the main control used to keep the legacy record from continuing to behave like the active provider-backed subscription during future syncs. Microsoft supports the Excel Online workflow used for this type of bulk field update.

3. Archive related License Change Logs

Create a License Change Log view named ARI & ASP LCLs and filter for:

Status Reason = Active
Subscription contains data
Related Subscription Provider Part Number begins with DZH318Z09V6F
Related Subscription Family = NCE:RESERVEDINSTANCE
Related Subscription Purchase Type = MicrosoftCsp:ReservedInstance

Include the Status Reason column, export the results to Excel Online, and update only:

Status Reason = Archived

This archive step comes from your migration procedure. It also aligns with Work 365’s general billing model, where License Change Logs are part of subscription lifecycle and invoicing history, so legacy license-based records and their active change history should not remain in the active billing path once the new Recon-based records take over.

4. Delete related Scheduled License Change Logs

Create a Scheduled License Change Log view named ARI & ASP SLCLs and filter for:

Status Reason = Pending and, if applicable, Archived
Subscription contains data
Related Subscription Provider Part Number begins with DZH318Z09V6F
Related Subscription Family = NCE:RESERVEDINSTANCE
Related Subscription Purchase Type = MicrosoftCsp:ReservedInstance

Export the results first and keep that file for reference. Then delete the legacy scheduled records. If you need to delete a large number of records, use Bulk deletion instead of manual cleanup. This view logic and export-first sequence come from your migration procedure, and Microsoft supports bulk deletion for this kind of targeted cleanup.

5. Allow subscription sync to recreate the records

After the legacy records are deactivated and the related logs are cleaned up, allow the scheduled subscription sync to run. Your migration procedure notes that this can take up to 24 hours in many environments. After sync completes, the new ARI and ASP records should be recreated as Recon-based subscriptions. Current Work 365 documentation supports that end state by documenting Reserved Instance and Savings Plans billing as reconciliation-driven. If Scheduled License Change Logs are still needed afterward, recreate them only where there is a valid business need.

6. Verify the migration

Review the ARIs & ASPs subscription view and confirm that active records now show:

Billing Type = Recon Based
Family = NCE:RESERVEDINSTANCE for Azure Reserved Instances
Family = NCE:AZURE for Azure Savings Plans
Purchase Type = MicrosoftCsp:ReservedInstance for Azure Reserved Instances
Subscription ID in the expected long composite format noted in your migration procedure

Also review the ARI & ASP LCLs view and confirm that the related License Change Logs are now marked Archived.

Treat the migration as complete when:

the old license-based records are inactive
the new recon-based records are present
the related logs have been archived or removed as appropriate

Those verification details come from your procedure, while the target-state Recon model is consistent with current Work 365 documentation.

Troubleshooting

Expected ARI or ASP records do not appear in the initial view

Recheck the filter logic and validate the values in Provider Part Number, Family, and Purchase Type on the subscription records. Those are the identifying filters called out in your migration procedure.

Legacy subscriptions are still being matched during sync

Confirm that the old records were updated with the old- prefix on Subscription ID before the next sync ran. In your migration procedure, that prefix is the main control used to prevent the new Recon-based sync from matching back to the old legacy record.

Excel updates do not save back correctly

Verify that you used the supported Excel Online workflow and kept the existing workbook structure intact. Microsoft notes that formatting and unsupported workbook changes can interfere with saving data back to the model-driven app.

Large Scheduled License Change Log cleanup is impractical manually

If you need to delete a large volume of Scheduled License Change Logs, use Bulk deletion instead of manual cleanup, then review the job status and any failures from the Power Platform admin center.