Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Azure VM lifecycle, AWS EC2 instance retirement, and Google Compute Engine deprecation are different kinds of policy—not three names for the same shutdown process. Azure’s lifecycle tracks VM size series; AWS’s cited retirement process addresses an individual instance when its underlying hardware has an irreparable failure; and Google Cloud documents listed feature deprecations separately from instance states and host-maintenance behavior. Before acting on a notice, identify exactly what it applies to, what date and configuration govern it, and what will happen to the running workload.

What “lifecycle” means at each cloud provider

A notice that a cloud resource is “retiring” can describe a product lifecycle, a fault on one physical host, a feature being withdrawn, or a maintenance event. Those situations have different triggers and consequences. Treating them as equivalent can lead to the wrong migration plan—for example, assuming a workload will be moved automatically when the provider’s policy instead deallocates or terminates it.

Provider mechanism What it applies to What triggers action What to establish first
Azure VM size-series lifecycle A VM size series, rather than an individual VM’s hardware failure The series advances through published lifecycle stages toward retirement; separate capacity restrictions may apply The series, its stage and retirement date, any capacity restriction, and cloud geography
AWS EC2 instance retirement An individual EC2 instance AWS detects an irreparable failure of the instance’s underlying hardware The scheduled event and whether the instance uses an EBS root volume or an instance-store root volume
Google Cloud Compute Engine deprecation and maintenance Depending on the notice: a listed feature, an instance state, or host-maintenance behavior A feature reaches its published deprecation schedule, an instance changes state, or a host event occurs Which mechanism the notice describes, plus the relevant machine type and configuration

These distinctions come from the providers’ documentation: Microsoft Learn’s Azure VM lifecycle overview and retirement FAQ, AWS’s EC2 instance-retirement guide, and Google Cloud’s feature-deprecation, instance-state, and host-maintenance pages. The dated examples below reflect those pages as accessed on October 11, 2026. Provider schedules and supported configurations can change, so check the current notice for the affected resource before planning a production change.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How Azure VM lifecycle stages work

Microsoft describes four Azure VM size-series stages: Current, Extended, End of Life, and Retired. The lifecycle applies to a size series. It is not a general retirement clock for every Azure VM, and it does not mean a particular VM has suffered a hardware fault.

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Stage What it means operationally
Current The series is in the Current stage of Microsoft’s documented lifecycle.
Extended The series has advanced to the Extended stage. Confirm the series-specific guidance and available targets when planning a change.
End of Life Retirement has been announced, but the size remains available until its retirement date. The announcement is a planning deadline, not proof that the VM has already stopped.
Retired The size is no longer available to create a VM, resize into, or run. Microsoft says VMs still on the retired size are deallocated; they stop working, cease incurring charges, and no longer have an SLA or support.

The key distinction is between an announced retirement and the retirement itself. An End of Life notice creates time to assess compatibility and move the workload. Once the size is Retired, a VM left on it cannot continue running in that size. Microsoft’s stated consequences also mean you should not treat deallocation as a supported migration or as a guarantee that the workload will resume on a replacement size without operator work.

Capacity restrictions are a separate signal

Microsoft distinguishes capacity-growth restrictions from the retirement date. A restriction can affect deployment or expansion before the size is retired. A series can therefore present an immediate capacity-planning issue while its formal retirement is still in the future. The lifecycle overview and capacity notices need to be checked together; a future retirement date alone does not establish that you can still scale out or resize freely today.

Microsoft’s lifecycle FAQ says capacity-growth restrictions for Dv3, Dsv3, Ev3, and Esv3 began in July 2026, while the stated retirement date for those series is November 15, 2029. The gap between those dates illustrates why capacity availability and lifecycle status are different questions, not a universal grace period for all VM series.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Current Azure example: Dv3, Dsv3, Ev3, and Esv3

In the Microsoft Learn FAQ reviewed October 11, 2026, all 32 sizes in the Dv3, Dsv3, Ev3, and Esv3 series are listed as retiring on November 15, 2029. Microsoft says this retirement does not apply to Azure Government, Azure operated by 21Vianet, or sovereign cloud regions. Do not extend that exception—or the date—to other series or deployments without checking the current lifecycle information for the subscription’s cloud and affected size.

Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

The published date is a useful planning input, not a substitute for checking a resource-specific notice or current capacity restrictions. If the workload is in an excluded cloud, verify its applicable policy rather than assuming the commercial Azure schedule controls it.

What happens to an Azure VM when its size is retired?

At retirement, a VM still using the affected size is deallocated, according to Microsoft’s lifecycle guidance. It stops working, stops incurring charges, and no longer has an SLA or support. Deallocation is not the same as the VM being migrated to a newer series, nor is it continued service on the old size. Plan and validate a move before the retirement date if the workload must remain available.

Preparation should be based on the workload’s actual requirements, not simply on finding a size with a similar name. Microsoft advises operators to assess feature compatibility and modernize to a supported Current or Extended series. Some migrations require series-specific preparation, so check the guidance for both the retiring series and the intended target.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  1. Identify the affected resources. Inventory VMs by exact size series and size, region, and cloud environment. Match them to the lifecycle notice rather than relying on a broad product-family label.
  2. Check both retirement and capacity information. Record the formal retirement date and any earlier restriction that could affect new deployment, expansion, or resizing.
  3. Choose a supported target. Compare the workload’s required capabilities with candidate Current or Extended series. Follow any migration preparation specific to the source or target series.
  4. Test the workload on the target. Validate application behavior and operational requirements before committing a production change. The lifecycle schedule does not establish that two sizes are functionally interchangeable.
  5. Schedule and complete the change before the deadline. Allow for the workload’s validation and maintenance needs; do not plan around the assumption that the old size will keep running after retirement.
  6. Recheck the notice near the change. Confirm the applicable date, capacity status, and geography for the subscription and resources before executing the migration.

How AWS EC2 instance retirement differs

The AWS guide cited here describes instance retirement as a response to AWS detecting an irreparable failure in the underlying hardware for an individual EC2 instance. This is not a lifecycle progression for an EC2 instance family or a portfolio-wide calendar of planned size retirements. The cited page says AWS sends an email containing the instance ID and retirement date; the event is specific to the affected instance.

Rank #3
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.

The most important operational detail is the root-volume type. The response differs materially between an EBS-root instance and an instance-store-root instance:

EC2 root storage What happens at retirement What the operator should plan for
EBS root The instance is stopped. It can be restarted, at which point it moves to new hardware. Review the scheduled event and prepare for the stop and restart. Confirm that the workload and its data are ready for that recovery path.
Instance-store root The instance is terminated and cannot be used again. Plan recovery or replacement rather than expecting to restart the same instance. Account for the fact that this instance itself is not reusable.

Do not apply Azure’s four size-series stages to an AWS hardware-retirement event. Conversely, do not infer from the EC2 guide that every AWS instance has a scheduled retirement date. The relevant starting point is the actual event notice, the identified instance, and its root storage.

Responding to an EC2 retirement notice

  1. Match the notice to the instance. Use the instance ID and retirement date in AWS’s email to locate the affected resource and inspect its scheduled event.
  2. Determine the root storage. Establish whether the instance is EBS-root or instance-store-root. The distinction determines whether AWS’s documented outcome is stop-and-restart on new hardware or termination with no reuse.
  3. Prepare the appropriate recovery. For an EBS-root instance, plan around the stop and subsequent restart. For an instance-store-root instance, arrange the workload and data recovery needed to replace a terminated instance.
  4. Coordinate the change with the service. Identify application dependencies and operational owners, and choose a suitable response window where the workload requires one. The hardware event is specific to the affected instance.

The cited AWS page does not establish a single calendar of retirement dates for all EC2 instances. A date in an individual notice should therefore be treated as a resource-specific event, not a general deadline for an instance family.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Google Cloud: separate feature deprecation from host maintenance

Google Cloud’s documentation covers several related but distinct subjects. Its feature-deprecation policy applies only to features listed in the deprecation documentation. Separately, Compute Engine documents instance state transitions and host events. A notice about a listed feature does not, by itself, mean every VM using a particular machine type is being retired; a host-maintenance setting is not the same thing as a feature deprecation.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.

For a listed deprecated feature, Google’s policy gives the feature a defined availability period before shutdown is scheduled. Identify the exact feature and its dates in the deprecation table. The policy should not be generalized to unlisted features or read as a single retirement schedule for all Compute Engine instances.

Dated feature examples in Google’s table

The Google Cloud table reviewed October 11, 2026, lists NVIDIA P4 and T4 with a deprecation date of August 1, 2026, and shutdown date of August 1, 2027. As of October 13, 2026, the listed deprecation date has passed, while the stated shutdown date is still ahead. The same table lists CSEKs with deprecation on June 15, 2026, and shutdown on June 16, 2027; that deprecation date has also passed as of October 13, 2026.

These are examples tied to the named entries in Google’s feature table—not universal Compute Engine VM retirement dates. Confirm that a workload actually depends on the listed feature, then verify its current status and the applicable shutdown schedule before deciding how to change it.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What Google host maintenance may do to a VM

Google documents host-maintenance behavior separately from feature deprecation. Its host-maintenance overview says, “By default, most instances are set to live migrate during host events,” but the statement expressly excludes the instance types identified elsewhere on that page. Some machine types or configurations stop or terminate rather than live-migrate. “Most” is not “all,” so the default should never be treated as a guarantee for an individual VM.

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.

For a host-event notice, verify the affected machine type and configuration, and use the corresponding Google Cloud guidance to establish the supported maintenance behavior and response. For a feature notice, look up the named feature and its deprecation schedule. For an instance-state question, consult the separate instance-state documentation. The right response depends on which of these the notice actually describes.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

How to migrate a VM before a retirement or deprecation date

Migration is not one identical operation across the three providers. Azure’s size-series retirement calls for moving to a supported size before the old size is retired; AWS’s cited process is an instance-level hardware event with storage-dependent behavior; and a Google feature deprecation calls for addressing the feature, while host maintenance requires checking instance behavior. Use a notice-driven workflow rather than a provider-neutral assumption that the VM will be moved automatically.

  1. Classify the notice. Write down the affected object: an Azure size series, one EC2 instance, a Google-listed feature, or a Google host-maintenance condition. If the notice does not make this clear, resolve that before selecting a migration action.
  2. Capture the applicable date and scope. Record the event or shutdown date, the affected resource identifiers, region or cloud, and any stated configuration exceptions. For Azure, distinguish capacity restrictions from retirement; for AWS, use the date in the specific instance notice; for Google, use the relevant feature entry or host-maintenance guidance.
  3. Establish the actual running-workload outcome. Determine whether the policy says the VM remains available until a date, is deallocated, is stopped and can be restarted, is terminated, live-migrates, or may stop or terminate. Do not substitute one provider’s behavior for another’s.
  4. Identify dependencies and data implications. Map the application and its data to the affected VM, including storage behavior that changes the recovery path. The AWS root-volume distinction is especially consequential; for Azure or Google, follow the notice and configuration-specific guidance.
  5. Select a supported target or recovery path. For Azure, evaluate a supported Current or Extended size series and any series-specific preparation. For AWS hardware retirement, plan according to root storage. For Google, decide whether the change concerns a listed feature or a host-maintenance response.
  6. Validate before the deadline or event. Test the application’s required capabilities and recovery steps in an appropriate environment. The provider’s lifecycle dates identify a policy boundary; they do not certify the workload’s compatibility with a replacement.
  7. Set an operational window and ownership. Assign responsibility for the change, identify affected service owners, and choose timing that fits the workload’s availability needs. Maintain enough lead time to address failed validation rather than waiting until the final day.
  8. Reconfirm current provider guidance. Retirement tables, feature schedules, supported configurations, and geography exceptions can change. Check the current provider documentation and the resource’s actual notice before making the production change.

A practical comparison for cloud operators

Decision point Azure VM size-series lifecycle AWS EC2 instance retirement Google Compute Engine
Scope A VM size series An individual instance identified in its event notice A listed feature, instance state, or host event, depending on the documentation and notice
Trigger Published progression through lifecycle stages toward retirement; capacity limits can occur separately AWS detects irreparable failure of the instance’s underlying hardware A listed feature’s deprecation schedule, an instance-state transition, or a host event
Notice or deadline Check lifecycle stage, retirement date, capacity notice, and geography The cited guide describes an email with the instance ID and retirement date; no portfolio-wide calendar is established there Check the entry for the listed feature or the relevant host-maintenance guidance; no universal VM retirement date follows from these mechanisms
Possible running-workload result At retirement, remaining VMs are deallocated and stop working; Microsoft says charges stop and SLA and support no longer apply EBS-root instance stops and can be restarted on new hardware; instance-store-root instance is terminated and cannot be reused A listed feature is available for its defined period before shutdown is scheduled; for host events, most instances default to live migration, while some types or configurations stop or terminate
Operator’s first action Check both retirement and capacity information, then select and validate a supported target Inspect the event and root-storage type, then plan for the corresponding recovery path Determine whether the issue is feature deprecation, instance state, or host maintenance; inspect the relevant feature, machine type, and configuration

Questions to answer before acting on any notice

  • What exactly is changing? A size series, one instance due to host hardware, a listed cloud feature, or host-maintenance behavior?
  • What event triggers the action? Is the date a published retirement, a resource-specific scheduled event, a feature shutdown date, or a maintenance event?
  • What happens to the running workload? Does it remain available until the deadline, deallocate, stop, terminate, or live-migrate—and is that outcome explicitly applicable to this configuration?
  • Which exceptions matter? Check geography and cloud type, region, machine series, root storage, machine type, and any configuration called out by the provider.
  • What target preserves the required behavior? Confirm workload capabilities and the migration or recovery steps, rather than choosing only by a similar resource name.

These questions keep the comparison useful without implying that the providers operate one shared lifecycle system. For Azure, the central planning task is to move off a retiring size series and account for earlier capacity limits. For AWS, it is to respond to the event for the affected instance based on its root storage. For Google Cloud, it is to distinguish a listed feature’s schedule from a VM’s state or host-maintenance behavior.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.