Requirement related to Governance, Retention, Legal Hold, eDiscovery in SharePoint Online
Hi All, I have requirement related to Governance, Retention, Legal Hold, eDiscovery in SharePoint Online. How can I start and where can I get more information and implementation details around these topics? Which are the important points to be considered for this requirement ? Thanks, PratikMicrosoft Launches Copilot for All Initiative
The Microsoft 365 Copilot Chat app is the free to use chat app available to commercial Microsoft 365 customers. The free chat app now supports Copilot agents, including agents that are grounded against Graph data (on a pay-as-you-go metered basis). The free chat app is highly functional and Microsoft hopes that it will convince customers to buy the full-fledged Copilot. https://office365itpros.com/2025/01/16/microsoft-365-copilot-chat-jan25/Blocking Microsoft 365 Copilot Making Inferences in Teams Meetings
The Copilot inference and evaluation policy controls if users can ask Copilot in Teams to evaluate the emotions of other meeting participants. It sounds creepy that meeting participants can ask Copilot how someone is feeling based on their contributions to a meeting, but AI is happy to answer unless blocked by policy. Maybe blocking big brother monitoring should be the norm rather than an exception? https://office365itpros.com/2024/12/19/copilot-inference-and-evaluation/Introducing new Storage Capabilities to Copilot in Azure (Preview)
We are excited to announce that customers can now take advantage of new Copilot in Azure (Public Preview) capabilities for Storage services. Copilot in Azure is an intelligent assistant designed to help you design, operate, optimize and troubleshoot your Azure environment. With the new Storage capabilities, Copilot in Azure can analyze your storage services metadata and logs to streamline and enhance tasks such as building cloud solutions, managing, operating, supporting, and troubleshooting cloud applications in Azure Storage. Troubleshooting Disk Performance with Copilot in Azure Available now in Public Preview Azure offers a rich variety of Disk metrics, providing insights into the performance of your Virtual Machine (VM) and Disk. These metrics help you diagnose performance issues when your application requires higher performance than what you have configured for the VM and Disks. Whether you are looking to set up and validate a new environment in Azure, or are facing issues with your existing set-up, Copilot further enhances your experience by analyzing these metrics to troubleshoot performance issues on-behalf of you, along with providing guided recommendations for optimizing the VM and disks performance to improve the experience for your application. To troubleshoot performance issues with Copilot in Azure, navigate to Copilot in the Azure Portal and enter a prompt related to VM-Disk performance, such as “Why is my Disk slow?”. Copilot will then ask you to specify the VM and Disk(s) experiencing performance issues, along with the relevant time period. Using this information, you can use Copilot to analyze your current VM-Disk configuration and performance metrics to identify whether your application is experiencing slowness due to reaching the configured performance limits for the VM or Disk. It will then provide a summary of the analysis and a set of recommended actions to resolve your performance issue, which you can apply directly in the Portal through Copilot’s guided recommendations. By leveraging the power of Copilot, you can efficiently diagnose and address performance issues within your Azure Disks environment. For more information on the Disk Performance Copilot capability, refer to the Public Documentation. Managing Storage Lifecycle Management with Copilot in Azure Available now in Public Preview With Copilot in Azure, we're providing a more efficient way to manage and optimize your storage costs. Copilot in Azure allows you to save on costs by tiering blobs that haven't been accessed or modified for a while. In some cases, you might even decide to delete those blobs. With Copilot in Azure, you can simply automate lifecycle management (LCM) rule authoring, enabling you to perform bulk actions on Storage accounts through a natural language interface. This means no more manual rule creation or risk of misconfiguration! To use this capability, simply enter a prompt related to cost management, such as “Help me reduce my storage account costs” or “I want to lower my storage costs.” Copilot will then guide you through authoring an LCM rule to help you achieve your goals. For more information on the Storage Lifecycle Management Copilot capability, refer to the Public Documentation. Troubleshoot File Sync errors with Copilot in Azure Available now in Public Preview With Copilot in Azure, you can now quickly troubleshoot and resolve common Azure File Sync issues, such as network misconfiguration, incorrect RBAC permissions, or accidental file share deletions. Copilot in Azure detects errors and misconfigurations, provides exact steps to fix them, and can act on your behalf to resolve common errors. To use this capability, simply enter a prompt related to File Sync such as “Why are my files not syncing?” or “Help me troubleshoot error 0x80C83096.” With the File Sync errors troubleshooting skill, Copilot in Azure acts as your intelligent assistant to keep your File Sync environment running smoothly. This capability not only saves you time by cutting down on troubleshooting efforts but also empowers you to resolve issues confidently and independently. For more information on the Files Sync Copilot capability, refer to the Public Documentation.What’s new and coming to Microsoft Outlook – Ignite 2024
Since its launch, Copilot in Outlook has helped you manage and triage your email, providing drafting assistance, summaries, and insights to help you save time. Whether you need help drafting the appropriate email response, schedule meetings in a few clicks, find key information in an email thread, or make sure your message has the right tone and clarity, Copilot can help you achieve your goals. During Ignite, we added to our efforts to help you manage your inbox, and showed you how you can manage your meetings easier using Copilot, and also dived into the latest updates to the new Outlook for Windows and what to expect in the coming year. Let’s take a look at the capabilities we announced this week! Manage meetings easier with Copilot in Outlook We spend a lot of time in meetings during our work hours, sometimes as high as 60% of our time can be spent between meetings, emails, and chats. Even scheduling a meeting can take up to 15 mins, but Copilot can make this a little easier. Copilot now helps you schedule 1:1s and focus time, just ask Copilot to find some time with someone in your org and it will find the optimal time. Because Copilot is grounded on your organization’s data, it knows who your close collaborators are so you can ask Copilot something like “Schedule a meeting with my manager for next week” or “Schedule a meeting with Caitlin for next week” and Copilot will know to whom you are referring. Do you need time to finish a project? No problem – Ask Copilot to find reserve focus time for next week, “Find 3 hours of focus time next week before Wednesday”, and done! Now you can focus on your project. Schedule one-on-one meetings using Copilot in Outlook Meetings can make it easier to make decisions, iron details, or discuss ideas but sometimes it’s hard to keep them on track and focused. Making sure your meeting has an agenda can help you stay on track and make sure you are tackling the important points – Copilot can draft an agenda for you based on your input, just open the meeting invite, select “Draft with Copilot”, and provide some input like “Review the Contoso project, introduce a new team member, and discuss sales plan”. Copilot creates an agenda which you can easily edit. Once you are ready, just remember to send the invite. Use Copilot in Outlook to draft an agenda for your meeting Sometimes, you need to schedule a meeting with more than one person, but have you had to schedule a meeting to bring a long email to a conclusion? Reading and summarizing long email threads is time consuming and finding time between multiple people can be challenging, unless you have Copilot. Without leaving the conversation, Copilot can help you schedule a meeting to bring that long email thread to closure – Just select the “Schedule with Copilot” button and Copilot will get you ready for that meeting, it will i) Summarize the entire thread, ii) Create an agenda, and iii) find a time that works. Quick and easy, schedule a meeting in just a few clicks. Get help from Copilot to schedule a meeting based on an email conversation A new way to draft emails We all need some help sometimes writing an email, whether you are having writer’s block to start or you want to rewrite some parts of it – The new drafting with Copilot experience can help. We’ve updated the drafting experience to make it native to the compose window in Outlook, added suggested prompts so you can kick off your draft without even typing, and allow you to rewrite parts of your message with Copilot. Is it hard to choose which draft iteration is the best one? No worries, we’ve added the ability for you to review and choose between all the suggested drafts. So, whether you need a little help to get started or a lot of help to make sure you have the best message, Copilot has you covered. New Outlook for Windows showing the new drafting with Copilot experience What is new andcoming to the new Outlook for Windows The new Outlook for Windows is a reimagined experience designed to be more agile and innovative. With faster feature deployment and availability, it brings the latest Microsoft 365 Copilot capabilities and delivers a consistent experience across Windows. As we continue to work on your feedback to bring you the best experience for the new Outlook for Windows, there are some updates we want to share. Where we are We reached General Availability for commercial customers this year and are still in opt-in phase with optional policies for organizations that want to move their users into new Outlook. To see all our adoption content please visit https://aka.ms/newOutlookAdoption and continue sending us your feedback at https://aka.ms/newOutlookFeedback to help us prioritize our work. What to expect Over the past few years, we have been in an opt-in phase for the new Outlook. As we plan to transition to an opt-out model, some organizations have already begun migrating on their own. We anticipate that small and medium-sized businesses (SMBs) with Microsoft 365 for business plans will begin to be moved into this phase starting in January 2025, and with customers withMicrosoft 365 for enterprises licenses following in 2026. Importantly, there will still be an option to revert to the previous version if needed. In the coming year, we expect more organizations to expand their piloting and planning efforts for the new Outlook. During this phase, we encourage you to file DCRs and submit feedback both within the app and through your account teams. Graph showing the current state and estimated timelines What to do next The new Outlook migration journey has 3 main steps. Pre-migration, migration, and post-migration. Pre-Migration: During pre-migration, admins and their IT teams should learn as much as they can about the migration - What the migration entails and the implications for their organization. This also involves early migration piloting. Migration: The migration step is when the migration is executed. Piloting continues and the migration process evolves and becomes more extensive. Post-Migration: Finally, in post-migration, IT is wrapping up the activities from the second step. They’re also decommissioning the previous experience and learning to improve subsequent migrations. Graph showing the migration stages for the new Outlook for Windows Plan your migration Review the migration kit - https://aka.ms/newOutlookAdoption Admin control options - https://aka.ms/newOutlookControlRelease Learn about policy management - Policy Management - Deploy Office Prepare to manage updates and set up early adopters on Targeted Release Transition from COM to web add-ins - Migrate from COM to web add-ins and review a list of available web add-ins. We hope all these updates help you be more productive, save time, and plan your migration to the next phase. Please, keep sending us your feedback – It really helps us focus our work. Thanks!GitHub Copilot Global Bootcamp
GitHub Copilot Bootcamp is a series of four live classes designed to teach you tips and best practices for using GitHub Copilot. Discover how to create quick solutions, automate repetitive tasks, and collaborate effectively on projects.REGISTER NOW! Why participate? GitHub Copilot is not just a code suggestion tool, but a programming partner that understands your needs and accelerates your work. By participating in the bootcamp, you will have the opportunity to: Master the creation of effective prompts. Learn to develop web applications using AI. Discover how to automate tests and generate documentation. Explore collaboration practices and automated deployment. Learn in your local language We will also have editions in other languages besides English: Spanish: https://aka.ms/GitHubCopilotBootcampLATAM Brazilian Portuguese: https://aka.ms/GitHubCopilotBootcampBrasil Chinese:https://aka.ms/GitHubCopilotBootcampChina Agenda The English sessions are scheduled for 12pm PST, 3pm ET, 2pm CT, and 1pm MT. 📅 February 4, 2025 Prompt Engineering with GitHub Copilot Learn how GitHub Copilot works and master responsible AI to boost your productivity. 📅 February 6, 2025 Building an AI Web Application with Python and Flask Create amazing projects with AI integration and explore using GitHub Copilot to simplify tasks. 📅 February 11, 2025 Productivity with GitHub Copilot: Docs and Unit Tests Automate documentation and efficiently develop tests by applying concepts directly to real-world projects. 📅 February 13, 2025 Collaboration and Deploy with GitHub Copilot Learn to create GitHub Actions, manage pull requests, and use GitHub Copilot for Azure for deployment. Who can participate? If you are a developer, student, or technology enthusiast, this bootcamp is for you. The classes are designed to cater to both beginners and experienced professionals. Secure your spot now and start your journey to mastering GitHub Copilot! 👉 REGISTER NOW!
Copy library from SharePoint On Premises to SharePoint Online
Hi, for my Copilot Agent I need my documents in Azure Blob Storage. I'm trying to use Copy my library from SharePoint On Premises to Azure Blob Storage directly. But in power automate flow I see no possibility to access library from SharePoint On Premises. If that is possible then guide me and it'll be a breeze for me. As a way around I tried to sync files from SharePoint On Premises to my local machine using One Drive business but there is some long path related issue and I couldn't make it. Otherwise idea is copy my files from SharePoint On Premises to SharePoint Online and then setup the Power Automate Flow to copy files to Azure Blob Storage. I'm done with second part for another library (SharePoint Online to Azure Blob Storage) but I'm not getting any idea how I can copy my site from On Premises to Online version of SharePoint. Someone referred me SPMT but I don't think that is going to help (https://learn.microsoft.com/en-us/sharepointmigration/how-to-use-the-sharepoint-migration-tool) Any guidance in this regard will be highly appreciated. Thanks Ahmad AhsanLeveraging GitHub Copilot for T-SQL Code Conversion: A Deep Dive into Code Explainability
Converting database code between different relational database management systems (RDBMS) is an essential part of database migration , especially when moving from Oracle’s PL/SQL to SQL Server’s T-SQL. Both Oracle and SQL Server have unique syntax, functions, and programming conventions that require significant adjustments when converting complex SQL queries, stored procedures, or functions. While manual conversion can be a painstaking process, GitHub Copilot, an AI-powered code assistant, can ease this burden by offering real-time suggestions and automating many aspects of the conversion. In the first part of this two-part blog, we explore howGitHub Copilot can be a powerful tool for code conversion, helping developers quickly adapt code from one language or framework to another. By providing context-aware suggestions and completions, Copilot simplifies the process of rewriting and refactoring code. In the second part, we dive deeper into Copilot’s explainability feature, showcasing how it enhances the code conversion process from Oracle to Azure SQL. Code explainability in GitHub Copilot refers to the tool’s ability to offer suggestions and comments that help developers understand what a given piece of code is doing. When dealing with database migrations, such as converting Oracle SQL code to Azure SQL (SQL Server), GitHub Copilot’s ability to explain, suggest, and refactor code can ease the transition. It can assist in making the conversion process smoother, more efficient, and less error-prone by explaining the logic behind Oracle-specific queries and suggesting corresponding changes in Azure SQL’s syntax We'll go through multiple examples, analyze the differences between the two languages, and show how GitHub Copilot handles these challenges. Understanding the Key Differences: PL/SQL vs T-SQL Before jumping into examples, it's important to understand few of the fundamental differences between PL/SQL (Oracle) and T-SQL (SQL Server): Syntax: While both are procedural SQL dialects, there are key differences in the way they handle variables, control structures, and flow control. Functions: Each platform has its own set of built-in functions (e.g., string manipulation, date handling, etc.), and these need to be mapped correctly during conversion. Error Handling: Error handling and exception management differ between the two, with PL/SQL using EXCEPTION blocks and T-SQL using TRY...CATCH. Cursor Handling: While both support cursors for iterating through results, their syntax differs. Leveraging GitHub Copilot for Oracle PL/SQL to SQL Server T-SQL Code Conversion: A Deep Dive into Complex Examples with Explainability Converting database code between different relational database management systems (RDBMS) is an essential part of database migration , especially when moving from Oracle’s PL/SQL to SQL Server’s T-SQL. Both Oracle and SQL Server have unique syntax, functions, and programming conventions that require significant adjustments when converting complex SQL queries, stored procedures, or functions. While manual conversion can be a painstaking process, GitHub Copilot, an AI-powered code assistant, can ease this burden by offering real-time suggestions and automating many aspects of the conversion. In the first part of this two-part blog, we explore howGitHub Copilot can be a powerful tool for code conversion, helping developers quickly adapt code from one language or framework to another. By providing context-aware suggestions and completions, Copilot simplifies the process of rewriting and refactoring code. In the second part, we dive deeper into Copilot’s explainability feature, showcasing how it enhances the code conversion process from Oracle to Azure SQL. Code explainability in GitHub Copilot refers to the tool’s ability to offer suggestions and comments that help developers understand what a given piece of code is doing. When dealing with database migrations, such as converting Oracle SQL code to Azure SQL (SQL Server), GitHub Copilot’s ability to explain, suggest, and refactor code can ease the transition. It can assist in making the conversion process smoother, more efficient, and less error-prone by explaining the logic behind Oracle-specific queries and suggesting corresponding changes in Azure SQL’s syntax We'll go through multiple examples, analyse the differences between the two languages, and show how GitHub Copilot handles these challenges. Understanding the Key Differences: PL/SQL vs T-SQL Before jumping into examples, it's important to understand few of the fundamental differences between PL/SQL (Oracle) and T-SQL (SQL Server): Syntax: While both are procedural SQL dialects, there are key differences in the way they handle variables, control structures, and flow control. Functions: Each platform has its own set of built-in functions (e.g., string manipulation, date handling, etc.), and these need to be mapped correctly during conversion. Error Handling: Error handling and exception management differ between the two, with PL/SQL using EXCEPTION blocks and T-SQL using TRY...CATCH. Cursor Handling: While both support cursors for iterating through results, their syntax differs. Example 1: Complex Stored Procedure Conversion Let’s start with a complex example that involves handling parameters, cursors, and error handling. We'll look at a PL/SQL stored procedure in Oracle that processes employee records and outputs their details. CREATE OR REPLACE PROCEDURE GetEmployeeDetails (emp_id IN NUMBER) IS CURSOR emp_cursor IS SELECT employee_id, first_name, last_name, hire_date FROM employees WHERE employee_id = emp_id; emp_record emp_cursor%ROWTYPE; emp_full_name VARCHAR2(100); BEGIN OPEN emp_cursor; LOOP FETCH emp_cursor INTO emp_record; EXIT WHEN emp_cursor%NOTFOUND; -- Concatenate first and last name emp_full_name := emp_record.first_name || ' ' || emp_record.last_name; -- Output employee details DBMS_OUTPUT.PUT_LINE('Employee ID: ' || emp_record.employee_id); DBMS_OUTPUT.PUT_LINE('Full Name: ' || emp_full_name); DBMS_OUTPUT.PUT_LINE('Hire Date: ' || TO_CHAR(emp_record.hire_date, 'YYYY-MM-DD')); END LOOP; CLOSE emp_cursor; EXCEPTION WHEN NO_DATA_FOUND THEN DBMS_OUTPUT.PUT_LINE('No employee found with the given ID.'); WHEN OTHERS THEN DBMS_OUTPUT.PUT_LINE('An error occurred.'); END; Oracle PL/SQL Example In Oracle, we might have a procedure that uses a cursor to fetch employee records and print them. The procedure also includes error handling for potential issues during execution. Key Points in Oracle PL/SQL: Cursor: PL/SQL uses CURSOR for iterating through rows. Concatenation: Oracle uses || for string concatenation. Error Handling: PL/SQL uses EXCEPTION blocks for handling errors such as NO_DATA_FOUND. Converting to SQL Server T-SQL with GitHub Copilot When you type the PL/SQL code into an IDE with GitHub Copilot enabled (e.g., Visual Studio Code), Copilot will start suggesting the equivalent SQL Server T-SQL code. Here’s how Copilot converts the procedure. Copilot’s Suggested SQL Server T-SQL Code CREATE PROCEDURE GetEmployeeDetails (@emp_id INT) AS BEGIN DECLARE @emp_id INT, @first_name NVARCHAR(50), @last_name NVARCHAR(50); DECLARE @emp_full_name NVARCHAR(100); DECLARE emp_cursor CURSOR FOR SELECT employee_id, first_name, last_name, hire_date FROM employees WHERE employee_id = @emp_id; OPEN emp_cursor; FETCH NEXT FROM emp_cursor INTO @emp_id, @first_name, @last_name, @hire_date; WHILE @@FETCH_STATUS = 0 BEGIN -- Concatenate first and last name SET @emp_full_name = @first_name + ' ' + @last_name; -- Output employee details PRINT 'Employee ID: ' + CAST(@emp_id AS NVARCHAR); PRINT 'Full Name: ' + @emp_full_name; PRINT 'Hire Date: ' + CONVERT(NVARCHAR, @hire_date, 23); FETCH NEXT FROM emp_cursor INTO @emp_id, @first_name, @last_name, @hire_date; END CLOSE emp_cursor; DEALLOCATE emp_cursor; BEGIN TRY -- Error handling code (example) END TRY BEGIN CATCH PRINT 'An error occurred.'; END CATCH END; Key Points in T-SQL: Cursor: SQL Server uses DECLARE CURSOR to declare a cursor, similar to PL/SQL but with different syntax for opening and fetching. Concatenation: SQL Server uses + for string concatenation. Error Handling: SQL Server uses TRY...CATCH for error handling, unlike PL/SQL’s EXCEPTION block. GitHub Copilot provides a T-SQL equivalent for an Oracle PL/SQL stored procedure. Explanation of the Conversion Process Cursor Declaration and Fetching: PL/SQL uses CURSOR with OPEN, FETCH, and CLOSE to process rows. T-SQL uses DECLARE CURSOR to define the cursor and fetches rows with FETCH NEXT. Both approaches are similar, but T-SQL requires explicit DEALLOCATE to release the cursor. Error Handling: PL/SQL uses EXCEPTION blocks to handle errors like NO_DATA_FOUND. T-SQL uses TRY...CATCH blocks to capture and handle errors, a major difference in error handling between the two systems. String Concatenation: PL/SQL uses || for concatenating strings, while T-SQL uses +. This is a simple yet crucial change when converting between the two dialects. Example 2: Complex Query with Date Handling Let’s now look at a query that involves date handling and conditional logic. These are often tricky when converting between PL/SQL and T-SQL due to differences in how each platform handles dates. Oracle PL/SQL Query Example SELECT employee_id, first_name, hire_date, CASE WHEN hire_date < TO_DATE('2000-01-01', 'YYYY-MM-DD') THEN 'Veteran' ELSE 'New Hire' END AS employee_status FROM employees WHERE hire_date BETWEEN TO_DATE('1990-01-01', 'YYYY-MM-DD') AND SYSDATE; Key Points in PL/SQL: TO_DATE: Used to convert strings into dates. SYSDATE: Returns the current system date. CASE: Used for conditional logic to categorize employees as either "Veteran" or "New Hire". Copilot’s Suggested SQL Server T-SQL Code SELECT employee_id, first_name, hire_date, CASE WHEN hire_date < CONVERT(DATE, '2000-01-01', 23) THEN 'Veteran' ELSE 'New Hire' END AS employee_status FROM employees WHERE hire_date BETWEEN CONVERT(DATE, '1990-01-01', 23) AND GETDATE(); Key Points in T-SQL: CONVERT: SQL Server uses CONVERT for date formatting, similar to Oracle’s TO_DATE, but with different syntax and style codes. GETDATE(): Equivalent to Oracle’s TO_DATE In conclusion, GitHub Copilot streamlines code conversion by offering both quick suggestions and detailed explanations. The first part highlighted its ability to assist with code transitions, while the second part focused on how its explainability feature enhances the Oracle to Azure SQL migration, providing guided, efficient, and error-free conversion. This combination accelerates development and reduces potential issues during migration.Restricted Content Discovery
SharePoint Advanced Management includes a feature called "Restricted Content Discovery" aka RCD. The FAQs mention that: Restricted Content Discovery only affects tenant-wide search (SharePoint home, Office.com, Bing) and Microsoft 365 Copilot But then it goes on to mention: Restricted Content Discovery doesn't remove content from the tenant search index. and: Restricted Content Discovery is a site-level property. I completely understand that its intended use is to give organisations time to review and/or audit permissions and deploy access controls while onboarding Copilot in a safe manner. My focus is custom search solutions and custom apps that use search and should respect the RCD property. Being a property and the content remains in the index, it could be interpreted that RCD feature only works in the named services i.e. SharePoint Home, Office.com, Bing and Microsoft Copilot and it does not apply in Micrsoft Search, custom organisation-wide Search solutions e.g. using PnP-Search, API calls using the Graph etc. Is that the case? Also can the property be queried and retrieved using the Search API or is it limited to PowerShell?
