Create and share Copilot agents in SharePoint in a few clicks
Go behind the scenes to learn more about Copilot agents in SharePoint, powered by your content. What could be better? Copilot agents are built in Copilot Studio via our new, built-in lightweight agent builder experience in SharePoint. CJ and Karuana discuss the broader vision of Copilot agents and show you how to put this new capability to work within your SharePoint sites in Microsoft 365 - including IT management details and licensing insights. Check out the new Microsoft 365 Copilot agents in SharePoint adoption hub: https://aka.ms/SharePoint/agents. In addition, review the recent, related blog, "Microsoft 365 Copilot Wave 2: AI Innovations in SharePoint and OneDrive" by Adam Harmetz and Jason Moore. And review this short explainer video, "Copilot agents in SharePoint" taken from the "Microsoft 365 Copilot: Wave 2" event with Satya Nadella and Jared Spataro event broadcast - watch now:[FIXED] Legacy Edge extensions on Windows store after installing the new Edge
Today I came across this extension when browsing Windows store https://www.microsoft.com/store/productId/9P59WXTBHZZM I could install it without any issue but the thing is it doesn't work when I have the Stable version of Chromium based Edge installed. clicking "launch" opens the new Edge only, nothing else happens. I think the proper way to handle this situation is to either hide these extensions from Windows store once the new Edge is installed, OR show a message to user that: "it's not compatible with the current installed version of Edge browser". My suggestion is to add the new Chromium based Add-ons to the Windows store to be easily available and installed by users. https://microsoftedge.microsoft.com/April 2025 Recap: Azure Database for PostgreSQL Flexible Server
Hello Azure Community, April has brought powerful capabilities to Azure Database for PostgreSQL flexible server, On-Demand backups are now Generally Available, a new Terraform version for our latest REST API has been released, the Public Preview of the MCP Server is now live, and there are also a few other updates that we are excited to share in this blog. Stay tuned as we dive into the details of these new features and how they can benefit you! Feature Highlights General Availability of On-Demand Backups Public Preview of Model Context Protocol (MCP) Server Additional Tuning Parameters in PG 17 Terraform resource released for latest REST API version General Availability of pg_cron extension in PG 17 General Availability of On-Demand Backups We are excited to announce General Availability of On-Demand backups for Azure Database for PostgreSQL flexible server. With this it becomes easier to streamline the process of backup management, including automated, scheduled storage volume snapshots encompassing the entire database instance and all associated transaction logs. On-demand backups provide you with the flexibility to initiate backups at any time, supplementing the existing scheduled backups. This capability is useful for scenarios such as application upgrades, schema modifications, or major version upgrades. For instance, before making schema changes, you can take a database backup, in an unlikely case, if you run into any issues, you can quickly restore (PITR) database back to a point before the schema changes were initiated. Similarly, during major version upgrades, on-demand backups provide a safety net, allowing you to revert to a previous state if anything goes wrong. In the absence of on-demand backup, the PITR could take much longer as it would need to take the last snapshot which could be 24 hours earlier and then replay the WAL. Azure Database for PostgreSQL flexible server already does on-demand backup behind the scenes for you and then deletes it when the upgrade is successful. Key Benefits: Immediate Backup Creation: Trigger full backups instantly. Cost Control: Delete on-demand backups when no longer needed. Improved Safety: Safeguard data before major changes or refreshes. Easy Access: Use via Azure Portal, CLI, ARM templates, or REST APIs. For more details and on how to get started, check out this announcement blog post. Create your first on-demand backup using the Azure portal or Azure CLI. Public Preview of Model Context Protocol (MCP) Server Model Context Protocol (MCP) is a new and emerging open protocol designed to integrate AI models with the environments where your data and tools reside in a scalable, standardized, and secure manner. We are excited to introduce the Public Preview of MCP Server for Azure Database for PostgreSQL flexible server which enables your AI applications and models to talk to your data hosted in Azure Database for PostgreSQL flexible servers according to the MCP standard. The MCP Server exposes a suite of tools including listing databases, tables, and schema information, reading and writing data, creating and dropping tables, listing Azure Database for PostgreSQL configurations, retrieving server parameter values, and more. You can either build custom AI apps and agents with MCP clients to invoke these capabilities or use AI tools like Claude Desktop and GitHub Copilot in Visual Studio Code to interact with your Azure PostgreSQL data simply by asking questions in plain English. For more details and demos on how to get started, check out this announcement blog post. Additional Tuning Parameters in PG17 We have now provided an expanded set of configuration parameters in Azure Database for PostgreSQL flexible server (V17) that allows you to modify and have greater control to optimize your database performance for unique workloads. You can now tune internal buffer settings like commit timestamp, multixact member and offset, notify, serializable, subtransaction, and transaction buffers, allowing you to better manage memory and concurrency in high-throughput environments. Additionally, you can also configure parallel append, plan cache mode, and event triggers that opens powerful optimization and automation opportunities for analytical workloads and custom logic execution. This gives you more control for memory intensive and high-concurrency applications, increased control over execution plans and allowing parallel execution of queries. To get started, all newly modifiable parameters are available now through the Azure portal, Azure CLI, and ARM templates, just like any other server configuration setting. To learn more, visit our Server Parameter Documentation. Terraform resource released for latest REST API version A new version of the Terraform resource for Azure Databases for PostgreSQL flexible server is now available, this brings several key improvements including the ability to easily revive dropped databases with geo-redundancy and customer-managed keys (Geo + CMK - Revive Dropped), seamless switchover of read replicas to a new site (Read Replicas - Switchover), improved connectivity through virtual endpoints for read replicas, and using on-demand backups for your servers. To get started with Terraform support, please follow this link: Deploy Azure Database for PostgreSQL flexible server with Terraform General Availability of pg_cron extension in PG 17 We’re excited to announce that the pg_cron extension is now supported in Azure Database for PostgreSQL flexible server major versions including PostgreSQL 17. This extension enables simple, time-based job scheduling directly within your database, making maintenance and automation tasks easier than ever. You can get started today by enabling the extension through the Azure portal or CLI. To learn more, please refer Azure Database for PostgreSQL flexible server list of extensions. Azure Postgres Learning Bytes 🎓 Setting up alerts for Azure Database PostgreSQL flexible server using Terraform Monitoring metrics and setting up alerts for your Azure Database for PostgreSQL flexible server instance is crucial for maintaining optimal performance and troubleshooting workload issues. By configuring alerts, you can track key metrics like CPU usage and storage etc. and receive notifications by creating an action group for your alert metrics. This guide will walk you through the process of setting up alerts using Terraform. First, create an instance of Azure Database for PostgreSQL flexible server (if not already created) Next, create a Terraform File and add these resources 'azurerm_monitor_action_group', 'azurerm_monitor_metric_alert' as shown below. resource "azurerm_monitor_action_group" "example" { name = "<action-group-name>" resource_group_name = "<rg-name>" short_name = "<short-name>" email_receiver { name = "sendalerts" email_address = "<youremail>" use_common_alert_schema = true } } resource "azurerm_monitor_metric_alert" "example" { name = "<alert-name>" resource_group_name = "<rg-name>" scopes = [data.azurerm_postgresql_flexible_server.demo.id] description = "Alert when CPU usage is high" severity = 3 frequency = "PT5M" window_size = "PT5M" enabled = true criteria { metric_namespace = "Microsoft.DBforPostgreSQL/flexibleServers" metric_name = "cpu_percent" aggregation = "Average" operator = "GreaterThan" threshold = 80 } action { action_group_id = azurerm_monitor_action_group.example.id } } 3. Run the terraform initialize, plan and apply commands to create an action group and attach a metric to the Azure Database for PostgreSQL flexible server instance. terraform init -upgrade terraform plan -out <file-name> terraform apply <file-name>.tfplan Note: This script assumes you have already created an Azure Database for PostgreSQL flexible server instance. To verify your alert, check the Azure portal under Monitoring -> Alerts -> Alert Rules tab. Conclusion That's a wrap for the April 2025 feature updates! Stay tuned for our Build announcements, as we have a lot of exciting updates and enhancements for Azure Database for PostgreSQL flexible server coming up this month. We’ve also published our Yearly Recap Blog, highlighting many improvements and announcements we’ve delivered over the past year. Take a look at our yearly recap blog here: What's new with Postgres at Microsoft, 2025 edition We are always dedicated to improving our service with new array of features, if you have any feedback or suggestions we would love to hear from you. 📢 Share your thoughts here: aka.ms/pgfeedback Thanks for being part of our growing Azure Postgres community.Extensions are not being updated automatically nor manually if downloaded from Google web store
Extensions are not being updated automatically nor manually when a new version of them becomes available in Chrome web store where they were first downloaded from. one of those extensions are ublock origin. *when I say manually I mean going into extensions page and manually clicking on the update button. Edge Version 77.0.222.0 (Official build) canary (64-bit)PP3: deactivated extensions manager - notifications
PROBLEM (PP): 3 Classification: EXTENSIONS PRIORITY IN MY OPINION: 6 on a scale from 1 (low) to 10 (high) 1) Today i talk about a problem that i already reported to Google **1137157&hotlist_id=10394 and i see frequently in Edge too. I search i search and i search extension in the toolbar or extension box and i never find it. Since i have over 250 profiles, sometimes is difficult to remember if i installed it or not. So i try to reinstall the extension, and then i get such message. So Edge deactivated my extension. Like i asked to Google, i wish you could add a new panel for deactivated extensions and a way to reactivate at once all extensions. 2) Similar problem is ***1134182&hotlist_id=10394 about deactivated extension after sync activation which i have never seen until now in Edge (hope i will never see too). In case this happens in Edge too, add ability to approve all extensions at once, instead of showing me 20+ notifications for each edge profile. If you implement the deactivate panel like 1) we would fix this problem too. 3) since we are talking about extensions, i report you *1144126&hotlist_id=10394 another problem i noted recently in chrome, in the hope that edge dev can fix it, if this problem is available in edge too. i noted this problem even with 360chrome. 8+ minutes where you simply showed me 200 notifications about extensions crash. Please check that you avoid to show me 1000 messages if there is a total crash. At least in google was automatically, in 360chrome i needed to approve each crash one by one; after 20 i relaunched the browser (much faster). 4) about google chrome removed extension topic ***1143025&hotlist_id=10394 i haven't tested this in edge until now (or i have never seen such message), but would be cool that edge is able to sync deleted extensions (marked as malware by google) from chrome store (extensions, that are not available in edge store). Or to sync manual added extensions. we all know that google delete extensions in batch, would be cool that we can still use such extensions, that worked fine for months. Maybe you are already able to do that, or maybe not. I will test this in future. There are other problem with chrome, but not related to the topic extensions, so i prefer to report such problems only once i see in edge too.Name of the extensions need to be specific and not some wierd combination of letters
I have seen this issue when downloading the extensions from the Edge add-ons store and the Chrome web store and also sometimes when I get errors from the Extensions. The naming of extensions is seen like this - . Once I got an error in the console area about an extension but could not figure out which extension was it due to this naming system. I have sent feedback about this through the in-app feedback tool and hope that this issue is fixed as soon as possible.
