Hello Partners- 

Important to remember: Fundraising and Engagement is being retired. Support for Fundraising and Engagement will end at 11:59 PM Pacific Time on December 31, 2026. For more information, go to What’s new in Fundraising and Engagement.

Thanks!

​Hello Partners- 

We want to make you aware of the release of a Fundraising and Engagement update (Dynamics 365 only, version 2.5.3.1) that mitigates issues around Transaction and Payment scheduling.
 
The published documentation can be found here: What’s new in Fundraising and Engagement September 11, 2024 – Microsoft Cloud for Nonprofit | Microsoft Learn
 

Important to remember: Fundraising and Engagement is being retired. Support for Fundraising and Engagement will end at 11:59 PM Pacific Time on December 31, 2026. For more information, go to What’s new in Fundraising and Engagement.
 
Thanks!  Read More

​

I have been going round and round with “Microsoft” support but to no avail does this 3rd party know Teams.

So, let’s start easy, I have a client who is managed under GoDaddy so they do NOT have access to Admin. They do have access to Entra and Azure portals though.

They invited me as a guest in Azure. And all of a sudden I have a second account I can switch to in Teams.

I did the same invite in Azure for another client but I do NOT see a second sub-account to switch to. Why and what is the easy process to add sub accounts for my clients that I can switch to?

​I have been going round and round with “Microsoft” support but to no avail does this 3rd party know Teams. So, let’s start easy, I have a client who is managed under GoDaddy so they do NOT have access to Admin. They do have access to Entra and Azure portals though. They invited me as a guest in Azure. And all of a sudden I have a second account I can switch to in Teams. I did the same invite in Azure for another client but I do NOT see a second sub-account to switch to. Why and what is the easy process to add sub accounts for my clients that I can switch to?   Read More

​

We’ve got two upcoming public events for you. We’re ready to share, show, and engage! We got news, announcements, insights into using Microsoft Lists, and set to answer a lot of questions across Copilot, Teams, SharePoint, and more.

COMMUNITY CALL | Join in this month’s Copilot and M365 for SMB Community call | Tuesday, September 24, 2024, 12:10pm – 1:00pm PDT.
AMA | Join in the Microsoft Tools for Small and Medium Businesses AMA the following day | Wednesday, September 25, 9:00 – 10:00am PDT.

Community Call
Discover recent small and medium business (SMB) related announcements, learn about upcoming events, and “Get to know Microsoft Lists” – our special topic this month. We’ll conclude with an open discussion on anything covered during the call, or whatever is on your mind; we’d love to know and tackle any questions – including listening to any feedback.

Copilot and M365 for SMB Community call | Tuesday, September 24, 2024, 12:10pm – 1:00pm PDT

This month’s co-presenters:

Host & special topic: Mark Kashman – Senior Customer Experience Product Manager, SharePoint & Lists – Microsoft
Guest: Emily Swab – Senior Product Marketing Manager | Microsoft 365 for Small and Medium Businesses, Customer and Community – Microsoft
Discussion moderator: Gabe Ho – Senior Product Marketing Manager | Copilot for Microsoft 365 Adoption – Microsoft

Date/time: Tuesday, September 24, 2024, 12:10pm – 1:00pm PDT
Where: Online via Microsoft Teams | Use this public link to join the meeting LIVE: https://aka.ms/SMBCommunityCall 
Agenda: [September 24, 2024]

Welcome and announcements
Special topic: “Get to know Microsoft Lists” (see full segment abstract below)
Upcoming events
Open discussion (questions and feedback; turn your cameras on and unmute).

More about our special topic this month: “Get to know Microsoft Lists”
Get up-to-speed on the latest Microsoft Lists innovation and how it helps keep your sanity intact when tracking information. Be it in the early creation phase or in an ongoing flow of managing status and keeping everyone in sync – learn how to go from not-in-the-know to PRO! We’ll cover updates and insights across the Lists app, mobile value, Power Platform integration, within Teams collab, and more. Expect lots of demos of the latest features grounded in scenarios that resonate with everyone. Plus, lots of time for Q&A throughout + updated roadmap info on what’s coming next.

AMA
And don’t miss the “Microsoft Tools for Small and Medium Businesses AMA” the following day | Wednesday, Sept. 25, 9-10am PDT. This event is an opportunity to connect with Microsoft experts who can answer questions about how to utilize Microsoft tools to enhance your small or medium businesses.

Microsoft Tools for Small and Medium Businesses AMA | Wednesday, Sept. 25, 9-10am PDT.

AMA subject matter experts: 

Bryan Allen (Director, SMB Product Marketing, Microsoft 365) 
Abhijat Kanade (Principal Group SMB Product Manager, Microsoft Teams) 
Gabe Ho (Product Marketing, SMB Copilot for Microsoft 365) 
Melissa Torres (Principal Product Marketing Manager, SharePoint) 
Emily Swab (Senior Product Marketing, SMB Customer Advocacy) 

Date/time: Wednesday, September 25, 2024, 9:00am – 10:00am PDT 
Where: Live, chat-based event on this dedicated Microsoft Tech Community page

Our experts will be available to offer personalized advice and discuss the various features and best practices. To participate, simply post your questions in the comments section. We encourage you to submit your questions early and continue to engage throughout the one-hour session. All interactions take place in the Comments section without any video or live meeting components. Each question should be posted as a new comment to facilitate a smooth and organized discussion.

We hope to see you at both events! Stay connected with us in both the Copilot for Small and Medium Business and Small and Medium Businesses tech community spaces – blogs, discussions, and events.

Small business resources related to this month’s events

Help and learning for small business (support.microsoft.com)
Small Business resource center (microsoft.com)
Microsoft 365 Business Premium resources (Microsoft Learn)
+ Microsoft Lists resource center (adoption.microsoft.com)

Cheers, Mark

​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

​

Currently use Outlook.Live.Com (classic Outlook) to access Hotmail account.  Not having a cell phone, will I lose access Sep 16th?  Microsoft suggests to “get a newer Outlook email app which supports Modern Authentication”, but most customer reviews are very negative.  Can I use Windows Hello without downloading new Outlook?  Worried about messing up.  Please help.

​Currently use Outlook.Live.Com (classic Outlook) to access Hotmail account.  Not having a cell phone, will I lose access Sep 16th?  Microsoft suggests to “get a newer Outlook email app which supports Modern Authentication”, but most customer reviews are very negative.  Can I use Windows Hello without downloading new Outlook?  Worried about messing up.  Please help.  Read More

​

Hi community,

Here is my scenario.

User called in with the full primary mailbox.

User requested to enable Archive Mailbox.

I enabled In-Place Archive Mailbox.

Default MRM Policy states it should start move 2 years old email to archive mailbox, but it did not start doing it immediately.

Question is, how can we automatically start moving 2 years or 1 years old emails in In-Place Archive mailbox immediately instead of retention policy to kick in?

​Hi community, Here is my scenario.User called in with the full primary mailbox.User requested to enable Archive Mailbox.I enabled In-Place Archive Mailbox.Default MRM Policy states it should start move 2 years old email to archive mailbox, but it did not start doing it immediately.Question is, how can we automatically start moving 2 years or 1 years old emails in In-Place Archive mailbox immediately instead of retention policy to kick in?  Read More

​

Microsoft Loop’s Preview mode provides the ability to get the latest features, allowing users to explore and analyze them before deploying them to the entire organization, encouraging adoption.

​Microsoft Loop’s Preview mode provides the ability to get the latest features, allowing users to explore and analyze them before deploying them to the entire organization, encouraging adoption.  Read More

​

I am using Lightroom (Win) and exported an image then uploaded it to a Sharepoint Folder. The quality is great!

Now, I am trying to export another image, but when I do, it displays distorted.
I do not remember ‘how’ or what settings I used to export the first image, but when I look at the image details of both images, the dimensions are the same, but the DPI’s are not.

The details for original image that looks good are:
Dimensions: 4160 x 2768
Resolution: 72 DPI
Bit Depth: 24
Color Representation: sRGB

I cannot figure out how to lower the DPI to 72 when exporting the 2nd image, or if that even matters?
There is no resolution setting to change, only quality.

1) Does anyone know how to do that and maintain image quality?
2) Is there an Admin Sharepoint Setting that restricts photo quality? 

​I am using Lightroom (Win) and exported an image then uploaded it to a Sharepoint Folder. The quality is great!Now, I am trying to export another image, but when I do, it displays distorted.I do not remember ‘how’ or what settings I used to export the first image, but when I look at the image details of both images, the dimensions are the same, but the DPI’s are not.The details for original image that looks good are:Dimensions: 4160 x 2768Resolution: 72 DPIBit Depth: 24Color Representation: sRGBI cannot figure out how to lower the DPI to 72 when exporting the 2nd image, or if that even matters?There is no resolution setting to change, only quality.1) Does anyone know how to do that and maintain image quality?2) Is there an Admin Sharepoint Setting that restricts photo quality?   Read More

​

Hello.  I need help with a formula combining vlookup and match. Somehow, the return is not correct. My formula right now is:  VLOOKUP($B9,$B$2:$B$5,MATCH($A9,$A$2:$A$5,0),FALSE)

But it’s wrong apparently.  Why?

​Hello.  I need help with a formula combining vlookup and match. Somehow, the return is not correct. My formula right now is:  VLOOKUP($B9,$B$2:$B$5,MATCH($A9,$A$2:$A$5,0),FALSE) But it’s wrong apparently.  Why?  Read More

​

Just updated to 

​Just updated to Version 130.0.2831.0 (Official build) Canary (arm64) This massively breaks sharepoint.    Read More

​