Forum Widgets
Latest Discussions
Helping users navigate the rebrand to the "Microsoft 365 Copilot" App
This app/experience was formerly known as the Microsoft 365 App or by many just as the Microsoft 365 homepage (especially in the context of the browser and URLs like Microsoft365.com). Now that it's been rebranded to the Microsoft 365 Copilot app, I'm curious to know how peers are adapting their support for end users in regards to this change. If you want users to head to this app or web location to use Copilot Chat (in one of its forms - web or work) there isn't really much issue ("Go to the Microsoft 365 Copilot app to use Copilot"). But what these other scenarios? In the browser/or desktop app "Go to the Microsoft 365 Copilot app to modify your M365 Profile "Go to the Microsoft 365 Copilot app to download the desktop Office apps" "Go to the Microsoft 365 Copilot app to access PowerPoint in the browser. In the mobile app "Go to the Microsoft 365 Copilot app to update that PPT you've been working on while you're in an Uber." "Go to the Microsoft 365 Copilot app to capture pics of whiteboards and add them to your OneDrive" All these scenarios really have nothing to do with Copilot, but you've got to use the Copilot app...a little awkward right? (p.s. trying not to incent a riot about MSFT's naming skills) What makes it downright silly is if you've suppressed Copilot all together for users for whatever reason, right? To my understanding even if you've blocked Copilot Chat in your org, this app is still called Microsoft 365 Copilot... If I've misunderstood anything about the situation, please educate me. Otherwise, I'd love some thoughts on the group on how you are or are thinking about navigating this awkwardness with users.
Setup CatchAll-Mailbox for specific domain in Exchange
Hi, I want to introduce a CatchAll-Mailbox, meaning that all messages sent to non-existant recipients shall be redirected to a specific Mailbox. The basic idea is to introduce a rule that redirects all incoming messages and make an exception for recipients who are member of a Dynamic Group that contains all existing Mailboxes. To prevent exchange from instantly blocking the message and instead process the rules, i set the Accepted Domain to internal relay. Now i want to make this whole thing domain-specific, meaning it should only apply for unknown recipients of specificdomain.com. I tried to introduce a recipient-matches-pattern-condition but that didnt work. How can i set this up?SharePoint Online – Get tenant storage usage and total capacity with PowerShell and MgGraph cmdlets
In my search for at way to get data about SharePoint tenant storage usage and the total capacity, I have been using the PnP PowerShell module. I wanted to move away and use Microsoft Graph instead. I found inspiration in multiple places and have been cooking a little script that I wanted to share with the community. Info and the script can be found at my webpage: SharePoint Online - Get tenant storage usage with PowerShell and MgGraph cmdlets - Christoffer Klarskov Jakobsen - Microsoft Architect I hope some of you can use it :)
Loops table rules broken
When attempting to create a rule on a table in Loops, I get the following: The "here" opens the Loop in a new tab. MS Support, through our corporate support, responded that the Loops product team was deprecating this feature and taking it out of the UI. There is a Power Automate trigger based on Loop triggers. The above seems unlikely unless there is a replacement in the works, such as using Power Automate. Does anyone know what gives here?
Automatic version history not working for self created document libraries
Hi, Our SharePoint environment is currently using the default version history number of 500. We were looking at lowering this because we're just consuming way too much storage. Last year we noticed that there was a new way to manage version history, automatically, which is also recommended by Microsoft. I finally got my head wrapped around on how it works, and we're doing some testing on it on just a few sites, but when I set it on a document library outside of the default "Document" library that comes with the site, it doesn't work. Nothing is set to expire even though there is lots of documents with aged versions that should have seen expiry dates by now. When I set it the versioning to automatic on the default "Document" library, it seems to work, as I do see files that have expiry dates. Is anybody else having a similar experience trying to use automatic version history?
Create SharePoint Files from Azure Automation Runbooks
In this Practical Graph article, we describe how to create SharePoint files using an Azure Automation runbook. The code uses the Microsoft Graph PowerShell SDK whenever possible, but we had to resort to Graph API requests at times. We also look at how to update document metadata for the newly uploaded files. https://practical365.com/create-sharepoint-files-azure-automation/
