Hello Insiders! We released 130.0.2821.1 to the Dev channel! This includes numerous fixes. For more details on the changes, check out the highlights below.

Copilot+ PCs expand availability with new AMD and Intel silicon | Windows Experience Blog

Added Features:

Added a ‘Theme Description’ and ‘Theme Type Label’ section in the updated settings/appearance page.

Improved Behavior:

Resolved an issue where browser would crash after scanning a QR code during account transfer in an already installed case.
Resolved an issue when logging out of an MSA account caused browser to crash, preventing a successful logout on iOS.

Changed Behavior:

Fixed an issue where clicking the site icon on the taskbar controller did not work after opening the site side pane from the sidebar and minimizing the browser.
Resolved an issue where the Add Split Screen option was missing from the toolbar and only available in the ‘More’ menu.
Fixed an issue where tabs displayed URLs in ‘Tab groups’ from the Favorites/Collections group.
Resolved an issue where Autofill was not working for coupons in the browser.
iOS:

Fixed an issue where the font size of the ‘Microsoft Rewards’ page increased in landscape mode on iOS.
Resolved an issue where files sometimes could not be opened properly after downloading on iOS.
Resolved an issue where the NTP was broken after switching accounts in split screen mode on iOS.

Mac:

Fixed an issue where pressing ‘Esc’ did not exit full screen mode.
Resolved an issue where three extra lines appeared in full screen mode on Mac.
Resolved an issue where the ‘Pick a color’ function in the theme settings could not be used under ‘Settings and More’ on Mac.
Resolved an issue where the URL in the address bar was not properly visible after selection in Light mode with a theme applied on Mac.

Android:

Fixed an issue where the tooltip continued to display after clicking the back button and appeared in the wrong location under the extension on Android.
Fixed an issue when clicking on an Outlook link to open browser caused the browser title in the background to display ‘Microsoft Edge First Run Experience’ on Android.

See an issue that you think might be a bug? Remember to send that directly through the in-app feedback by heading to the … menu > Help and feedback > Send feedback and include diagnostics so the team can investigate.

Thanks again for sending us feedback and helping us improve our Insider builds.

~Gouri

​Hello Insiders! We released 130.0.2821.1 to the Dev channel! This includes numerous fixes. For more details on the changes, check out the highlights below.
Copilot+ PCs expand availability with new AMD and Intel silicon | Windows Experience Blog
 
Added Features:

Added a ‘Theme Description’ and ‘Theme Type Label’ section in the updated settings/appearance page.

Improved Behavior:

Resolved an issue where browser would crash after scanning a QR code during account transfer in an already installed case.
Resolved an issue when logging out of an MSA account caused browser to crash, preventing a successful logout on iOS.

Changed Behavior:

Fixed an issue where clicking the site icon on the taskbar controller did not work after opening the site side pane from the sidebar and minimizing the browser.
Resolved an issue where the Add Split Screen option was missing from the toolbar and only available in the ‘More’ menu.
Fixed an issue where tabs displayed URLs in ‘Tab groups’ from the Favorites/Collections group.
Resolved an issue where Autofill was not working for coupons in the browser.
iOS:

Fixed an issue where the font size of the ‘Microsoft Rewards’ page increased in landscape mode on iOS.
Resolved an issue where files sometimes could not be opened properly after downloading on iOS.
Resolved an issue where the NTP was broken after switching accounts in split screen mode on iOS.

Mac:

Fixed an issue where pressing ‘Esc’ did not exit full screen mode.
Resolved an issue where three extra lines appeared in full screen mode on Mac.
Resolved an issue where the ‘Pick a color’ function in the theme settings could not be used under ‘Settings and More’ on Mac.
Resolved an issue where the URL in the address bar was not properly visible after selection in Light mode with a theme applied on Mac.

Android:

Fixed an issue where the tooltip continued to display after clicking the back button and appeared in the wrong location under the extension on Android.
Fixed an issue when clicking on an Outlook link to open browser caused the browser title in the background to display ‘Microsoft Edge First Run Experience’ on Android.

 
See an issue that you think might be a bug? Remember to send that directly through the in-app feedback by heading to the … menu > Help and feedback > Send feedback and include diagnostics so the team can investigate.
Thanks again for sending us feedback and helping us improve our Insider builds.
 
~Gouri  Read More

​

Cloud marketplaces continue to increase in popularity as the preferred way for organizations to find, try, and buy software—especially as cloud and AI needs continue to become more complex.  

The Microsoft commercial marketplace is central to how we sell alongside you, our partners, to help you reach more customers, simplify sales, and unlock growth. To support you with more ways to service your customers, Microsoft now empowers partners in Canada, the United Kingdom, and the United States to sell professional services through private offers in the marketplace. 

For software development companies, you often need to account for a variety of services to support your product sales. Whether that’s assisting with implementation, training your customers, or providing support over the long-term, the value of your teams’ time and resources can be accounted for directly within your marketplace sales with professional services for private offers. And, for other partners like systems integrators, managed service providers, etc., they can provide professional services (through a private offer) to support their customers who prefer the simplicity of purchasing through the marketplace.  

The value for you and your customers 

As customers shift to marketplaces to centralize their cloud portfolio, they can further simplify purchasing by streamlining software and services purchases through one platform. Customers can get your solutions while buying directly from Microsoft, and have purchases consolidated directly on their Azure invoice. As a partner, you can skip the hassle of vendor onboarding while dramatically simplifying your sales—while reaching a global market. Plus, by bundling your software and service, you decrease time-to-value for your customer.  
 

“Now that professional services are offered within the Microsoft commercial marketplace, it gives us another path to service our customers with simplified selling. And we can bundle our service and product together, helping our customers cut through procurement red tape.”  –TeamViewer 

How it works 

For partners in eligible geographies, you can now:  

sell your professional services as a standalone private offer or  
attach your professional services to a private offer alongside your software. 

Examples of professional services include: assessments, briefings, customer support, implementation, migration, proof of concepts, and workshops. These professional services are sold as private offers. You can inform your customer that the private offer is ready directly from Partner Center when you build the offer. The customer then receives an email that directs them to the Azure portal. Assuming they have proper permissions, the customer will accept and purchase the professional services private offer. With the private offer, you can also negotiate your terms and use flat-rate billing plans including upfront, monthly, or annual payments for up to three years

Any company who is part of the Microsoft AI Cloud Partner Program can sell professional services. Details are provided in our documentation, but at a high-level: 
 

Be a member of the Microsoft AI Cloud Partner Program (it’s free to join) 
Sign the marketplace publisher agreement 
Publish your offer
Sell professional services private offers  

Get started with marketplace 

The Microsoft commercial marketplace is dedicated to helping you reach more customers, simplify sales, and unlock growth. If you’re building an application and looking to maximize marketplace success, consider joining ISV Success. Partners who join get access to free benefits, designed to help you build across the Microsoft Cloud, publish faster, and grow your partnership opportunity. Get details on how to join in the ISV Hub. 

To get started selling professional services, check out the technical documentation. 

​Microsoft Tech Community – Latest Blogs –Read More 

Introduction

Design Considerations

When designing this script for automating Azure VM snapshot creation, several key considerations were prioritized to enhance efficiency and user experience:

1. Subscription Handling

All-Subscription Search: The script loops through all Azure subscriptions associated with the account. This design ensures that the script can locate the VM across any subscription without manual intervention to switch between them. This is particularly useful for environments with multiple subscriptions.

2. Dynamic VM Search

Automatic VM Discovery: Instead of requiring users to manually input resource group and subscription details, the script dynamically searches for the VM by its name across all subscriptions. This automation simplifies the process and reduces the likelihood of errors.

3. Snapshot Naming Convention

Consistent Naming Format: Snapshots are named using the format VMname_diskname_dd-MM-yyyy_HH_mm. This approach ensures that snapshots are well-organized and easily identifiable. The script also removes random characters, such as GUIDs, often appended to disk names, resulting in clean and consistent snapshot names.

4. OS and Data Disk Snapshots

Comprehensive Backup: The script separately handles snapshots for both the OS disk and data disks. This ensures that all disks attached to the VM are included in the backup process, providing complete coverage.

5. Time Efficiency

Streamlined Process: The script is designed to eliminate the need for repeated manual input and navigation within the Azure portal. By simply providing the VM name, users can automate the entire process, from VM identification to snapshot creation. This saves considerable time and effort, particularly in environments with many VMs and subscriptions.

By focusing on these design considerations, the script offers a robust and user-friendly solution for automating VM snapshot creation across Azure subscriptions.

Prerequisites

To use this script, you need:

Azure PowerShell module installed (Az module).Active Azure account with sufficient permissions to access VMs and create snapshots across subscriptions.A VM name as input.

Why Automate Snapshot Creation?

In many organizations, virtual machines (VMs) are critical for running services, and regularly creating snapshots of these VMs is essential for disaster recovery and version control. Traditionally, creating snapshots for Azure VMs involves several manual steps:

Log in to the Azure Portal: Access the Azure portal to start the snapshot creation process.Navigate Through Subscriptions: Switch between different Azure subscriptions to find the correct VM.Locate the Correct VM: Search for and select the specific VM for which you want to create snapshots.Create Snapshots: Manually create snapshots for both the OS disk and any attached data disks.Repeat the Process: Perform these steps for each disk across multiple VMs or subscriptions.

This manual process is not only time-consuming but also prone to errors. Automating snapshot creation simplifies and streamlines the process:

Reduces Manual Effort: The entire process can be accomplished with a few clicks.Saves Time: Automation eliminates the need to repeat steps across multiple VMs and subscriptions.Minimizes Errors: By automating the process, you reduce the risk of human error.

With the automation script, you only need to provide the VM name, and the script handles the rest, making snapshot management more efficient and reliable.

Script Overview

Below is the PowerShell script that automates the process of creating snapshots for a VM across multiple subscriptions in Azure:

<#
.SYNOPSIS
This script automates the process of creating snapshots for a virtual machine (VM) in Azure across multiple subscriptions.
The script will locate the VM by its name, determine the resource group where it exists, and create snapshots for both the
OS disk and any attached data disks. It ensures that the snapshot names follow a specific naming convention while removing
any random characters appended to the disk names.

.DESCRIPTION
– Loops through all Azure subscriptions attached to the account.
– Searches for a specified VM by name across all subscriptions.
– Identifies the resource group of the VM.
– Creates snapshots for the OS disk and all data disks in the same resource group as the VM.
– Follows the snapshot naming convention: computername_diskname_dd-mm-yyyy_hh_mm.
– Removes random characters (e.g., GUIDs) after the disk name in snapshot naming.

.NOTES
Author: Vivek Chandran
Date Created: 11-09-2023

#>

# Login to Azure (if not already logged in)
Connect-AzAccount

# Prompt the user to enter the VM name
$computerName = Read-Host -Prompt “Please enter the name of the VM you want to snapshot”

# Get all subscriptions available to the account
$subscriptions = Get-AzSubscription

# Loop through each subscription to find the specified VM
foreach ($subscription in $subscriptions) {
# Set the subscription context so that all subsequent commands target this subscription
Set-AzContext -SubscriptionId $subscription.Id

# Retrieve all VMs in the current subscription
$vms = Get-AzVM

# Check if a VM with the specified name exists in this subscription
$vm = $vms | Where-Object { $_.Name -eq $computerName }

if ($vm) {
# Output message indicating the VM was found
Write-Host “VM ‘$computerName’ found in subscription ‘$($subscription.Name)'”

# Retrieve the resource group where the VM resides
$resourceGroup = $vm.ResourceGroupName

# Loop through each data disk attached to the VM and create a snapshot
foreach ($disk in $vm.StorageProfile.DataDisks) {
# Get the name of the data disk
$diskName = $disk.Name

# Remove any random characters from the disk name after the first underscore (if present)
$cleanedDiskName = ($diskName –split ‘_’)[0..1] –join ‘_’

# Get the current date and time in the format ‘dd-MM-yyyy_HH_mm’ for use in the snapshot name
$currentDateTime = Get-Date -Format ‘dd-MM-yyyy_HH_mm’

# Construct the snapshot name using the cleaned disk name and the date/time
$snapshotNameWithDataDisk = “$computerName-$cleanedDiskName-$currentDateTime”

# Define the snapshot configuration using the disk’s managed disk ID
$snapshotConfig = New-AzSnapshotConfig -SourceUri $disk.ManagedDisk.Id -Location $vm.Location -CreateOption Copy -AccountType Standard_LRS

# Create the snapshot in the same resource group as the VM
New-AzSnapshot -Snapshot $snapshotConfig -ResourceGroupName $resourceGroup -SnapshotName $snapshotNameWithDataDisk

# Output message indicating that the snapshot was successfully created for the data disk
Write-Host “Snapshot created for data disk: $snapshotNameWithDataDisk”
}

# Create a snapshot for the OS disk of the VM
$osDisk = $vm.StorageProfile.OsDisk

# Get the name of the OS disk
$osDiskName = $osDisk.Name

# Remove any random characters from the OS disk name after the first underscore (if present)
$cleanedOsDiskName = ($osDiskName –split ‘_’)[0..1] –join ‘_’

# Get the current date and time in the format ‘dd-MM-yyyy_HH_mm’ for use in the snapshot name
$currentDateTime = Get-Date -Format ‘dd-MM-yyyy_HH_mm’

# Construct the snapshot name using the cleaned OS disk name and the date/time
$snapshotNameWithOSDisk = “$computerName-$cleanedOsDiskName-$currentDateTime”

# Define the snapshot configuration using the OS disk’s managed disk ID
$snapshotConfig = New-AzSnapshotConfig -SourceUri $osDisk.ManagedDisk.Id -Location $vm.Location -CreateOption Copy -AccountType Standard_LRS

# Create the snapshot in the same resource group as the VM
New-AzSnapshot -Snapshot $snapshotConfig -ResourceGroupName $resourceGroup -SnapshotName $snapshotNameWithOSDisk

# Output message indicating that the snapshot was successfully created for the OS disk
Write-Host “Snapshot created for OS disk: $snapshotNameWithOSDisk”

# Exit the loop since the VM has been found and processed
break
} else {
# Output message indicating that the VM was not found in this subscription
Write-Host “VM ‘$computerName’ not found in subscription ‘$($subscription.Name)'”
}
}

# Output a final message indicating that the snapshot process has completed
Write-Host “Snapshots process completed!”

How the Script Works

1. Azure Authentication

Connect to Azure: The script starts by authenticating the user to Azure using the Connect-AzAccount command. If the user is already logged in, this step is skipped.

2. Input the VM Name

Prompt for VM Name: After successful authentication, the script prompts you to enter the name of the virtual machine (VM) you want to create snapshots for.

3. Subscription Looping

Retrieve Subscriptions: The script retrieves all Azure subscriptions associated with the account using Get-AzSubscription.Check Each Subscription: It iterates through each subscription to check if the specified VM exists. When the VM is found, the script switches the context to that subscription using Set-AzContext.

4. Snapshot Creation

Data Disk Snapshots: For each data disk attached to the VM, the script creates a snapshot. It follows a consistent naming convention that includes the VM name, disk name, and timestamp to ensure clarity and organization.OS Disk Snapshot: After handling the data disks, the script creates a snapshot for the OS disk, using the same naming convention.

5. Completion

Confirmation Message: Once all snapshots (for both OS and data disks) are created, the script outputs a message confirming the successful completion of the snapshot creation process.

Conclusion

This PowerShell script has greatly improved my workflow for managing Azure VMs. By automating the snapshot creation process, it eliminates the need to manually log into the Azure portal, locate the VM, and create snapshots for each disk individually. Instead, I can simply run the script, provide the VM name, and let it handle the entire process.

For anyone managing multiple Azure subscriptions and seeking a reliable method to automate snapshot creation, this script offers a quick and effective solution. It ensures that backups are created consistently and stored properly, enhancing overall backup management and efficiency.

​Introduction Managing virtual machines in Azure can be time-consuming, especially when creating snapshots across multiple subscriptions. Typically, this involves logging into the Azure portal, manually locating the VM, and creating snapshots for both the OS disk and attached data disks an inefficient and tedious process. To simplify this, I developed a PowerShell script that automates snapshot creation, allowing me to create snapshots by simply inputting the VM name. This script is part of my toolkit for automating repetitive Azure tasks. It iterates through all subscriptions linked to my Azure account, identifies the specified VM, and generates snapshots for both the OS and data disks within the VM’s resource group, adhering to a consistent naming convention. This article describes the script, the rationale behind its design, and how it improves the efficiency of managing Azure resources. Design ConsiderationsWhen designing this script for automating Azure VM snapshot creation, several key considerations were prioritized to enhance efficiency and user experience: 1. Subscription HandlingAll-Subscription Search: The script loops through all Azure subscriptions associated with the account. This design ensures that the script can locate the VM across any subscription without manual intervention to switch between them. This is particularly useful for environments with multiple subscriptions. 2. Dynamic VM SearchAutomatic VM Discovery: Instead of requiring users to manually input resource group and subscription details, the script dynamically searches for the VM by its name across all subscriptions. This automation simplifies the process and reduces the likelihood of errors. 3. Snapshot Naming ConventionConsistent Naming Format: Snapshots are named using the format VMname_diskname_dd-MM-yyyy_HH_mm. This approach ensures that snapshots are well-organized and easily identifiable. The script also removes random characters, such as GUIDs, often appended to disk names, resulting in clean and consistent snapshot names. 4. OS and Data Disk SnapshotsComprehensive Backup: The script separately handles snapshots for both the OS disk and data disks. This ensures that all disks attached to the VM are included in the backup process, providing complete coverage. 5. Time EfficiencyStreamlined Process: The script is designed to eliminate the need for repeated manual input and navigation within the Azure portal. By simply providing the VM name, users can automate the entire process, from VM identification to snapshot creation. This saves considerable time and effort, particularly in environments with many VMs and subscriptions.By focusing on these design considerations, the script offers a robust and user-friendly solution for automating VM snapshot creation across Azure subscriptions. PrerequisitesTo use this script, you need:Azure PowerShell module installed (Az module).Active Azure account with sufficient permissions to access VMs and create snapshots across subscriptions.A VM name as input. Why Automate Snapshot Creation?In many organizations, virtual machines (VMs) are critical for running services, and regularly creating snapshots of these VMs is essential for disaster recovery and version control. Traditionally, creating snapshots for Azure VMs involves several manual steps:Log in to the Azure Portal: Access the Azure portal to start the snapshot creation process.Navigate Through Subscriptions: Switch between different Azure subscriptions to find the correct VM.Locate the Correct VM: Search for and select the specific VM for which you want to create snapshots.Create Snapshots: Manually create snapshots for both the OS disk and any attached data disks.Repeat the Process: Perform these steps for each disk across multiple VMs or subscriptions.This manual process is not only time-consuming but also prone to errors. Automating snapshot creation simplifies and streamlines the process:Reduces Manual Effort: The entire process can be accomplished with a few clicks.Saves Time: Automation eliminates the need to repeat steps across multiple VMs and subscriptions.Minimizes Errors: By automating the process, you reduce the risk of human error.With the automation script, you only need to provide the VM name, and the script handles the rest, making snapshot management more efficient and reliable. Script OverviewBelow is the PowerShell script that automates the process of creating snapshots for a VM across multiple subscriptions in Azure:<#
.SYNOPSIS
This script automates the process of creating snapshots for a virtual machine (VM) in Azure across multiple subscriptions.
The script will locate the VM by its name, determine the resource group where it exists, and create snapshots for both the
OS disk and any attached data disks. It ensures that the snapshot names follow a specific naming convention while removing
any random characters appended to the disk names.

.DESCRIPTION
– Loops through all Azure subscriptions attached to the account.
– Searches for a specified VM by name across all subscriptions.
– Identifies the resource group of the VM.
– Creates snapshots for the OS disk and all data disks in the same resource group as the VM.
– Follows the snapshot naming convention: computername_diskname_dd-mm-yyyy_hh_mm.
– Removes random characters (e.g., GUIDs) after the disk name in snapshot naming.

.NOTES
Author: Vivek Chandran
Date Created: 11-09-2023

#>

# Login to Azure (if not already logged in)
Connect-AzAccount

# Prompt the user to enter the VM name
$computerName = Read-Host -Prompt “Please enter the name of the VM you want to snapshot”

# Get all subscriptions available to the account
$subscriptions = Get-AzSubscription

# Loop through each subscription to find the specified VM
foreach ($subscription in $subscriptions) {
# Set the subscription context so that all subsequent commands target this subscription
Set-AzContext -SubscriptionId $subscription.Id

# Retrieve all VMs in the current subscription
$vms = Get-AzVM

# Check if a VM with the specified name exists in this subscription
$vm = $vms | Where-Object { $_.Name -eq $computerName }

if ($vm) {
# Output message indicating the VM was found
Write-Host “VM ‘$computerName’ found in subscription ‘$($subscription.Name)'”

# Retrieve the resource group where the VM resides
$resourceGroup = $vm.ResourceGroupName

# Loop through each data disk attached to the VM and create a snapshot
foreach ($disk in $vm.StorageProfile.DataDisks) {
# Get the name of the data disk
$diskName = $disk.Name

# Remove any random characters from the disk name after the first underscore (if present)
$cleanedDiskName = ($diskName -split ‘_’)[0..1] -join ‘_’

# Get the current date and time in the format ‘dd-MM-yyyy_HH_mm’ for use in the snapshot name
$currentDateTime = Get-Date -Format ‘dd-MM-yyyy_HH_mm’

# Construct the snapshot name using the cleaned disk name and the date/time
$snapshotNameWithDataDisk = “$computerName-$cleanedDiskName-$currentDateTime”

# Define the snapshot configuration using the disk’s managed disk ID
$snapshotConfig = New-AzSnapshotConfig -SourceUri $disk.ManagedDisk.Id -Location $vm.Location -CreateOption Copy -AccountType Standard_LRS

# Create the snapshot in the same resource group as the VM
New-AzSnapshot -Snapshot $snapshotConfig -ResourceGroupName $resourceGroup -SnapshotName $snapshotNameWithDataDisk

# Output message indicating that the snapshot was successfully created for the data disk
Write-Host “Snapshot created for data disk: $snapshotNameWithDataDisk”
}

# Create a snapshot for the OS disk of the VM
$osDisk = $vm.StorageProfile.OsDisk

# Get the name of the OS disk
$osDiskName = $osDisk.Name

# Remove any random characters from the OS disk name after the first underscore (if present)
$cleanedOsDiskName = ($osDiskName -split ‘_’)[0..1] -join ‘_’

# Get the current date and time in the format ‘dd-MM-yyyy_HH_mm’ for use in the snapshot name
$currentDateTime = Get-Date -Format ‘dd-MM-yyyy_HH_mm’

# Construct the snapshot name using the cleaned OS disk name and the date/time
$snapshotNameWithOSDisk = “$computerName-$cleanedOsDiskName-$currentDateTime”

# Define the snapshot configuration using the OS disk’s managed disk ID
$snapshotConfig = New-AzSnapshotConfig -SourceUri $osDisk.ManagedDisk.Id -Location $vm.Location -CreateOption Copy -AccountType Standard_LRS

# Create the snapshot in the same resource group as the VM
New-AzSnapshot -Snapshot $snapshotConfig -ResourceGroupName $resourceGroup -SnapshotName $snapshotNameWithOSDisk

# Output message indicating that the snapshot was successfully created for the OS disk
Write-Host “Snapshot created for OS disk: $snapshotNameWithOSDisk”

# Exit the loop since the VM has been found and processed
break
} else {
# Output message indicating that the VM was not found in this subscription
Write-Host “VM ‘$computerName’ not found in subscription ‘$($subscription.Name)'”
}
}

# Output a final message indicating that the snapshot process has completed
Write-Host “Snapshots process completed!”
 How the Script Works 1. Azure AuthenticationConnect to Azure: The script starts by authenticating the user to Azure using the Connect-AzAccount command. If the user is already logged in, this step is skipped. 2. Input the VM NamePrompt for VM Name: After successful authentication, the script prompts you to enter the name of the virtual machine (VM) you want to create snapshots for. 3. Subscription LoopingRetrieve Subscriptions: The script retrieves all Azure subscriptions associated with the account using Get-AzSubscription.Check Each Subscription: It iterates through each subscription to check if the specified VM exists. When the VM is found, the script switches the context to that subscription using Set-AzContext. 4. Snapshot CreationData Disk Snapshots: For each data disk attached to the VM, the script creates a snapshot. It follows a consistent naming convention that includes the VM name, disk name, and timestamp to ensure clarity and organization.OS Disk Snapshot: After handling the data disks, the script creates a snapshot for the OS disk, using the same naming convention. 5. CompletionConfirmation Message: Once all snapshots (for both OS and data disks) are created, the script outputs a message confirming the successful completion of the snapshot creation process. ConclusionThis PowerShell script has greatly improved my workflow for managing Azure VMs. By automating the snapshot creation process, it eliminates the need to manually log into the Azure portal, locate the VM, and create snapshots for each disk individually. Instead, I can simply run the script, provide the VM name, and let it handle the entire process.For anyone managing multiple Azure subscriptions and seeking a reliable method to automate snapshot creation, this script offers a quick and effective solution. It ensures that backups are created consistently and stored properly, enhancing overall backup management and efficiency.  Read More

​

It would be helpful to be able to drag & Drop files into a task in the new Planner app

​It would be helpful to be able to drag & Drop files into a task in the new Planner app  Read More

​

– High end laptop, passes Health Check, ready for 11

– running W10 Pro, fully up to date

– Windows Update shows “no updates” — no W11 UPGRADE

I do NOT want to blank install W11.

I need to upgrade in place to leave my configurations, settings, files, profiles, etc. alone.

Some of the MS W11 website options talk about INSTALL from media, ISO, etc. — not desired.

At one point months ago after seeing “update to W11” for the 100th time in Windows Update I clicked “I’ll stay on W10 for a while” or some such.  Do I need to “undo” that?  How?

This missing W11 update doesn’t seem to be “HIDDEN” in WUSHOWHIDE.

Please help

Thx

​- High end laptop, passes Health Check, ready for 11- running W10 Pro, fully up to date- Windows Update shows “no updates” — no W11 UPGRADEI do NOT want to blank install W11.I need to upgrade in place to leave my configurations, settings, files, profiles, etc. alone.Some of the MS W11 website options talk about INSTALL from media, ISO, etc. — not desired. At one point months ago after seeing “update to W11” for the 100th time in Windows Update I clicked “I’ll stay on W10 for a while” or some such.  Do I need to “undo” that?  How? This missing W11 update doesn’t seem to be “HIDDEN” in WUSHOWHIDE. Please help Thx  Read More

​