Skip to main content

Posts

Boosting Productivity with Microsoft 365 Copilot: A Guide for Experienced Microsoft 365 IT Professionals

  As seasoned Microsoft 365 consultants, leveraging cutting-edge tools to streamline workflows and enhance productivity is paramount. Microsoft 365 Copilot, an AI-powered assistant designed to augment Microsoft 365 applications, stands out as a revolutionary tool in this regard. Copilot integrates deeply within the Microsoft ecosystem, assisting with a range of tasks from drafting emails to developing complex Power Apps. In this blog post, we will explore the top five ways Microsoft 365 Copilot can increase productivity for experienced Microsoft 365 consultants, with a special focus on its capabilities in Power App development. 1. Streamlined Email and Document Drafting One of the most time-consuming tasks for information workers is drafting emails and documents. Microsoft 365 Copilot can significantly reduce the time spent on these activities through its intelligent suggestion capabilities. By analyzing the context and purpose of emails and documents, Copilot can suggest phras...

SharePoint 2013 - Event ID: 8319

EventID: 8319 This is the error and this is the EVENT NAME Table  SqlIo Data _Partition27 has 443957248 bytes that have exceeded the max bytes 442857142 Which is the SQL IO Usage event To know the database name Go to Central Admin  First, we must get the logging database name The database name is in this example "WSS_Logging" Now we need to find which table is taking most of the space inside the WSS logging Database. You can check from the  SQL Server Login to  SQL Server  Management Studio -> Select your logging Database (Right Click) -> Reports- > Standard Reports -> Disk Usage by Top Tables The SQL IO Usage event We can reduce the retention period of any events (default is 14) Table SqlIoData_Partition27 has 443957248 bytes that has exceeded the max bytes 442857142 In my case its SQL IO Any way if we couldn’t know exactly which identity is causing the problem we can just Set them all to any number o...

Forget SharePoint Adoption; Focus on Utilization!

SharePoint Adoption     Many SharePoint deployments stall or are never implemented throughout an organization.  These less than desired results are often use the excuse of a lack of SharePoint "adoption". Problems with "Adoption"      The whole idea of SharePoint "Adoption" implies a passive approach to rolling out a SharePoint deployment and a style of "build it and they will come" philosophy.  Generally, users, especially non-technical users, continue to do what they've always done out of habit or previous training.  Users will ONLY change their day-to-day tasks or tools if they are told to do so by their boss or if they're convinced a new tool or method can save them time or solve some obvious problem, such as daily tasks. Active Approach to drive Utilization      Any successful SharePoint deployment has to be proactively driven on a based on providing real and current solutions.  SharePoint deployments s...