Smarter Retention in Microsoft 365: A Step Toward Cleaner, More Relevant Data - Coming soon

on
Anyone who has worked with SharePoint management knows that data governance is a cornerstone of digital productivity, especially in large organizations where information can accumulate rapidly. Today, retention policies in Microsoft 365 allow administrators to manage data based on creation or modification dates. However, in my experience, this approach is not always sufficient. Files that haven’t been accessed in years may still linger in OneDrive or SharePoint, cluttering storage, slowing down search, and diluting the relevance of AI-powered tools like Microsoft 365 Copilot. A new feature in Microsoft Purview Retention Policies, expected this winter, promises to enhance Data Lifecycle Management. This upcoming setting will enable policies to identify files that have remained untouched for a specified period and automatically flag them for deletion or archival. This enhancement is particularly valuable for organizations leveraging Microsoft 365 Copilot. By removing outdated or irreleva...

An "important" lesson from day one at Lync 2013 Ignite

on
Lync 2013 comes with new features and new functionality. To support all of these new functions, there has been introduced a big set of new PowerShell cmdlets.
This didn't come as a surprise to me, as I have been playing around with the preview for a bit, and I have been reading Tom Arbuthnot's excellent post on the subject.
One of these "important" new cmdlets is the "Invoke-CsManagementServerFailover" command. Why?
Well, If you are anything like me, you type as little as possible, and you use the TAB as much as possible, you might to look out for this one. My "default" is to type "invoke-csma" + TAB. to get to the Invoke-"CsManagementStoreReplication" and then hit enter.

Unless I now hit enter twice, i will start the process of failing over the CMS.

I have no idea of how many times I'll fail over the CMS before I actually learn to hit tab twice, but I know I'll get there in the end.

So what was the important lesson here? It's not what you have to learn, but what you have to unlearn :)

For future reference, here's a list of all the cmdlets for Lync 2013