What does the archive experience for OneDrive look like after the change to unlicensed accounts?
Based on this change, OneDrive accounts will be set to archive: Unlicensed OneDrive accounts subject to a retention policy, retention period, or legal hold will be automatically archived after 93 days of license removal. https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts#enforcement-of-policy-changes-for-unlicensed-onedrive-accounts To test the experience, we attempted to run the PowerShell script used to archive a SharePoint site to a OneDrive site: Set-SPOSiteArchiveState https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spositearchivestate?view=sharepoint-ps However, it does not appear that a OneDrive site type is supported with this script. Does anyone know what "archived" actually means in the context of a OneDrive account? Also, what will the experience be both from a user perspective and from an admin perspective? In SharePoint, there's a message indicating the site is in an archived state and admins can see a list of all archived sites via the admin center. I think a lot of confusion would be avoided if OneDrive "sites" appeared in a list like SharePoint sites do within the SharePoint admin center. Thank you!Exchange archive mailbox migration license issue
Hi all, I have a situation where my environment is in a hybrid state with users ready to migrate. Some users are over 100GB but less 240GB, the Microsoft article on migrating large mailboxes says i have to provision the cloud archive first, but the documentation on this says i need a license. What's confusing me is if assign a license before they migrate this creates a whole new mailbox and all sorts of screwy thing happen and you have to clean up etc.. so, you instead assign the license after the migration.., but the cloud archive docu. is saying I need to assign a license for the cloud archive first. Has this changed where i can create the Cloud archive on-prem and migrate without needing a mailbox? am i missing something?How to Implement OAuth for a Bot-Based Message Extension App in Microsoft Teams for Graph API?
I have created a bot-based message extension app using the Teams Toolkit and need to call the Microsoft Graph API, which requires OAuth implementation. So far, I have created the app in the Teams Developer Portal, registered the app in Azure App registration, and registered the bot in the Bot Framework Developer Portal (dev.botframework.com). However, I am unclear about the OAuth flow and the specific configurations required. Can someone provide a detailed guide on how the OAuth flow works for a bot-based message extension in Microsoft Teams, the specific configurations needed in the Azure app registration, how to configure permissions and consent for accessing the Microsoft Graph API, and any additional settings required in the Teams Developer Portal or Bot Framework Developer Portal? Any guidance, code examples, or references to detailed documentation would be highly beneficial.
