Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
165258 stories
·
33 followers

US Officially a Measles Endemic Country

1 Share
An anonymous reader quotes a report from The Hill: The Pan American Health Organization (PAHO) confirmed Tuesday that it was withdrawing the U.S.'s measles elimination status, ending more than two decades of what is considered to be one of the greatest public health achievements in modern history. The U.S. met with PAHO's Measles and Rubella Elimination Regional Monitoring and Re-Verification Commission for a three-day, closed-door meeting last week. "The commission concluded that the endemic measles transmission has now been reestablished in Bolivia, Mexico and the United States, and recommended that their measles elimination status be withdrawn, a recommendation which I have accepted," Jarbas Barbosa, PAHO's director, said during the briefing Tuesday. The U.S. achieved measles elimination status in 2000 and has held onto that for more than 25 years. But the past two years have seen close to 8,000 measles infections and roughly a dozen related deaths. This year has been the worst in terms of transmission in more than 30 years. Erica Schwartz, director of the Centers for Disease Control and Prevention (CDC) has previously said losing elimination status won't lead to changes in the federal response. "We know where transmission is occurring and we've invested $100 million in state and local health departments to reach those communities," Schwartz said on Tuesday. "Losing a designation doesn't mean we abandon an evidence-based approach. It means we remain focused on stopping outbreaks."

Read more of this story at Slashdot.

Read the whole story
alvinashcraft
58 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Modernize applications and databases together with the Modernize CLI

1 Share

An application might need a framework upgrade, dependency updates, or a move to Azure. But behind that application is often a database that needs its own modernization decisions: Is the SQL Server workload ready to move? Which Azure SQL target is the best fit? What compatibility issues need to be addressed? How should the target be sized? And ultimately, how do you move the data safely?

With the GitHub Copilot modernization agent, delivered through the Modernize CLI, we are bringing these decisions closer together.

The modernization agent already provides an agentic workflow for application assessment, modernization planning, and execution. It can analyze applications and repositories, understand dependencies, create modernization plans, and orchestrate modernization work. 

Now, SQL Server migration assessment extends that experience to the database.

Start by understanding whether your SQL Server is ready to modernize

Before moving a database, you need evidence.

A SQL Server migration assessment helps answer several fundamental questions:

  • Can this workload move to Azure SQL?
  • What compatibility issues or migration blockers exist?
  • Which Azure SQL target is appropriate?
  • What configuration and capacity should the target use?
  • What could that target cost?

Our SQL migration work brings together four important lenses: compatibility, assessability, sizing, and pricing. The goal is not simply to produce a list of issues. It is to turn assessment evidence into a useful modernization decision: target fit, prioritized blockers, recommended compute and storage, and estimated cost with the assumptions behind it. 

This is important because compatibility alone does not answer the customer's real question.

Compatibility tells you whether you can move.

Sizing and pricing help tell you where you should land.

Bring SQL assessment into the Modernize CLI

With SQL Server migration capabilities in the Modernize CLI, you can assess the database as part of the same modernization workflow you use for your application.

Instead of switching between disconnected tools, reports, documentation, and calculators, the goal is to let the modernization agent invoke database-specific migration expertise when it recognizes that an application depends on SQL Server.

That expertise can evaluate readiness and help identify migration blockers, dependencies, target options, SKU guidance, and cost considerations. Our SQL migration skills are being designed around a skills-first model where specialized SQL expertise can be invoked by agents across developer and database experiences. 

Imagine starting with a simple modernization goal:

“Assess this application and its SQL Server database for modernization to Azure.”

The application assessment can analyze code, configuration, frameworks, and dependencies. The SQL assessment can then evaluate the database workload and its suitability for Azure SQL.

The result is a more complete picture of the workload rather than two independent assessments.

From a database assessment to a modernization decision

Finding an issue is useful. Understanding what to do next is much more valuable.

For a SQL Server workload, assessment results can help organize the migration decision around three questions.

  1. Is the workload ready?

The assessment identifies compatibility issues and conditions that could prevent or complicate migration. That gives you a clear starting point for remediation instead of discovering incompatibilities late in the migration process.

  1. Where should it run?

SQL Server modernization isn't simply a cloud-versus-on-premises decision. Depending on workload requirements, the destination might be Azure SQL Database, Azure SQL Managed Instance, SQL Server on Azure Virtual Machines, or other supported SQL targets.

The SQL migration agent is designed around helping customers assess, right-size, and move workloads across Azure SQL targets rather than forcing every workload through the same migration path. 

  1. What will the target look like and cost?

A migration recommendation becomes much more actionable when readiness is connected to sizing and pricing.

That means going beyond “this workload is compatible” and providing sufficient information to begin planning capacity, configuration, and cost.

Assessment is only the beginning

This is where an agentic approach becomes especially interesting.

The GitHub Copilot modernization agent already follows a workflow where assessment findings can become a modernization plan. The plan is reviewable and editable before execution, keeping people in control of the modernization process. 

We want the database journey to follow the same principle.

For SQL Server, the journey naturally progresses from:

Assess → Recommend → Plan → Migrate → Validate

Our broader SQL migration direction includes specialized skills for readiness and blockers, target and SKU guidance, prerequisites and remediation, migration using approaches such as BACPAC or LRS where applicable, and post-migration validation.

That changes the role of assessment.

Instead of assessment being a report that someone reads and then manually translates into another tool, the output can become context for the next agentic action.

If there is a migration blocker, the agent can help explain it and identify remediation.

If the workload is ready, it can help determine the next migration step.

If a target has been selected, it can help prepare a migration plan.

And, as migration capabilities expand, that same plan can become the basis for executing and validating the move.

Modernize the application and database as one workload

This is ultimately the bigger opportunity.

Customers don't operate applications and databases as independent modernization projects. The database is a dependency of the application, and changing one frequently affects the other.

The Modernize CLI already supports application assessment across individual or multiple repositories, including aggregated reports, dependency analysis, recommendations, and modernization planning. Batch assessment can also produce an aggregated view that helps organize applications into migration strategies and waves.

Adding SQL Server migration readiness creates the foundation for looking at the application and its database together.

For example, an application modernization assessment might identify:

  • application or framework changes,
  • application dependencies,
  • Azure service opportunities,
  • SQL Server dependencies,
  • database compatibility issues,
  • an Azure SQL target recommendation,
  • database sizing and cost considerations.

Rather than producing separate application and database projects, those findings can contribute to one modernization plan.

That is particularly important at estate scale.

An organization may have hundreds of applications and SQL Server instances. The challenge isn't simply assessing all of them. The real challenge is turning the results into decisions:

What is ready? What is blocked? What should we modernize first? Which workloads belong together? What is the expected effort and cost?

The Modernize CLI's batch-assessment capabilities already support per-repository and aggregated reports, including migration recommendations and migration-wave insights. Connecting database evidence to that model creates the potential for much richer application-and-database modernization planning. 

And then, move from assessment to migration

Assessment shouldn't be the end of the journey.

Our direction for SQL migration is to connect the stages that customers today frequently perform through separate experiences:

Discover → Assess → Recommend → Plan → Provision → Migrate → Validate

The SQL migration work already describes a longer-term workflow covering registration and discovery, migration readiness, blocker analysis, right-sizing, migration planning, execution, and validation.

The important difference is that these aren't simply additional commands.

They can become skills available to an agent.

The user states their goal. The agent determines which expertise is required. The skill performs the specialized operation and returns structured evidence. The agent then uses that evidence to determine the appropriate next step, while important or consequential actions remain subject to user review and approval. SQL migration guidance explicitly follows the principle that migration actions should require confirmation rather than being performed automatically. 

This gives us a model where:

AI recommends. Experts approve. Skills execute.

One modernization conversation

Consider where this can ultimately lead.

Instead of beginning a modernization project by asking which tool to open, a developer, DBA, architect, or migration engineer can start with the outcome:

“Modernize this application and its database to Azure.”

The agent can help break that goal into the work required:

  1. Assess the application.
  2. Identify its SQL Server dependency.
  3. Assess database migration readiness.
  4. Select an appropriate Azure SQL target.
  5. Identify blockers and required remediation.
  6. Build a modernization and migration plan.
  7. Review and approve the plan.
  8. Execute the application and database changes through the appropriate skills and tools.
  9. Validate the resulting environment.

The user remains in control, but no longer has to manually translate every finding from one tool into the next.

Modernization is becoming agentic

The GitHub Copilot modernization agent establishes the broader model: understand the existing environment, build a plan, let people review it, and then use agents and specialized capabilities to help perform the modernization. 

Bringing SQL Server migration readiness into that experience takes an important step toward treating the application and database as the connected workload they really are.

Today, you can start by assessing SQL Server migration readiness.

The next step is turning those assessment results into increasingly actionable migration decisions and workflows.

Learn More

Assess SQL Server Migration Readiness with the Modernize CLI - GitHub Copilot Modernization Agent

 

Read the whole story
alvinashcraft
59 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Windows Drivers Kit Support Update

1 Share

Dear Valued Customers,

We are updating the Windows Driver Kit (WDK) support model. Beginning June, 2027, Microsoft will focus support for native Windows driver development on the latest WDK release. A few older WDK versions will also remain supported to address compatibility needs.

For details on which versions are supported, please review:

Action required

Please ensure that you are using a supported WDK version by June, 2027. Under the updated support model, drivers developed using an unsupported WDK version will not be eligible for Windows Hardware Compatibility Program (WHCP) certification.

For questions or assistance, please contact your Microsoft support representative or wdksupport@microsoft.com.

Thank you for your continued partnership in building reliable, secure drivers for the Windows platform.

Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

Azure Functions Canvas (Preview): Build, run, and modernize Function Apps with GitHub Copilot

1 Share

If you use the GitHub Copilot app or Visual Studio Code, meet the Azure Functions canvas.

More and more developers now build with coding agents. The Azure Functions canvas helps you get more from that workflow. It addresses three common problems in Azure Functions development:

  • Use official templates without leaving your workflow. Get the same high-quality Azure Functions templates available in VS Code, directly in the GitHub Copilot app. Start building without switching tools.
  • Agents get there eventually, but slowly. A coding agent can produce an app that runs, but it can take many turns. You also can't always tell whether the result follows best practices.
  • Outdated choices cause incidents. Programming models, hosting plans, and runtime versions that reach end of support can cause outages. So can incorrect code or settings.

Canvases are new in the GitHub Copilot app. A canvas runs deterministic tasks quickly, without a round trip through the agent. It also gives you a visual workspace with state that you and the agent share. We're only starting to explore what canvases make possible.

Build faster with up-to-date templates

 

The canvas includes 90 starter and scenario templates for Azure Functions and Hosted Skills. They're more than samples: many include Bicep templates that deploy with the Azure Developer CLI (azd).

The canvas applies a template directly, so the agent needs fewer turns and less time to give you working code.

This is real code in your local work tree. You own the code and can extend it with GitHub Copilot, add it to your repository, and deploy it to Azure.

The canvas supports the full development loop: create, run locally, test, and deploy. You can also open your project in VS Code to continue development and debugging.

Select Triggers include Hosted Skills

Test your event-driven functions

Azure Functions is built for event-driven applications, but testing different triggers isn't always straightforward.

The Azure Functions canvas brings event-driven testing into your development workflow. It supports HTTP, Timer, Event Hubs, Service Bus, Storage Queue, Blob, Durable Functions, and Blob triggers with Event Grid.

Instead of switching between tools, you can test your functions as you build them, making it easier to develop and validate event-driven applications.

Run locally with Event Hubs Trigger

 

Build Hosted Skills with templates and an agent

With Hosted Skills, you build event-driven agents in natural language. The canvas includes 14 templates for them. Start from the template that matches your scenario to scaffold quickly, then let the agent continue. Built-in skills help the agent with creation, deployment, and configuration.

To build and test a Hosted Skill step by step, see Quickstart: Build and test a hosted skill with the Azure Functions hosted skills canvas.

Hosted Skills AI assisted coding

 

Modernize with confidence

On PaaS and serverless platforms, you must regularly review programming models, hosting plans, and supported runtime versions. This is important for security and reliability. Internal data from the Azure Functions team shows that 58% of incidents come from code or configuration issues. These issues are easy to miss. With the canvas, you can quickly find them in local projects and in apps deployed to Azure, and then have the agent fix them. Checks are read-only, and fixes need your approval.

Scan your app (local)Scan your app (Azure)

The canvas helps you follow current Azure Functions security and runtime best practices, from choosing supported configurations to identifying issues in existing applications.

Continue development in VS Code

Your project is real code, not a prototype locked inside the canvas.

Open it in VS Code to continue development with your familiar tools. The generated project includes configuration and infrastructure files to help you run locally and deploy to Azure.

Select Open In VSCodeVS Code integration

 

Available in seven languages

From day one, the canvas supports seven languages: English, Chinese (Simplified), German, Japanese, Korean, Portuguese (Brazil), and Spanish.

Translate feature

Get started

Find Azure Functions on Awesome GitHub Copilot, or install it from the marketplace: in the GitHub Copilot app, open Customize > Plugins, select Awesome Copilot, and install Azure Functions.

Pro tip: install it directly.

Start a new session, then ask:

Open Azure Functions canvas.

Use it in VS Code (Preview). Canvases are available in VS Code 1.142 and later for local sessions that use the Copilot harness. Install the plugin in the GitHub Copilot app as shown above. Then, in VS Code, enable chat.canvases.enabled, start a new session with the Copilot harness, and ask the agent to open the Azure Functions canvas. For details, see Canvases (Preview).

On Home, choose a task: Create, Open, Modernize, or Monitor. You don't need extra tools to open the canvas. To create from a template or deploy, install the Azure Developer CLI (azd). To run locally, install Azure Functions Core Tools 4. Check prerequisites in the canvas shows what you're missing.

Give it a try, and tell us what you think.

Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

Database Hub in Microsoft Fabric is generally available: your entire database estate in one place

1 Share

As applications grow, so does the database estate behind them. Many organizations now run hundreds or thousands of databases across cloud, hybrid and multicloud environments. The signals are already there: inventory, health, performance, security, risk and optimization. The hard part is making sense of them, knowing what needs attention and deciding what to do next.

Today, we're announcing the general availability of Database Hub in Microsoft Fabric. Database Hub gives you one place to see your whole estate, monitor it at scale and investigate where attention is needed. It covers Azure SQL, Azure Database for PostgreSQL, Azure Cosmos DB, SQL Server and SQL database in Fabric.

Everything in this release is built around that idea: one estate, every signal, wherever you work.

Get started for free

If you're new to Microsoft Fabric, you don't need to set anything up first. Open Database Hub, and you're automatically given a free Fabric license and taken straight to your estate. You only need Fabric capacity to share dashboards, create custom alerts or use Copilot.

Generally available today

AreaWhat you get
OverviewA "what needs attention" view across security, performance and optimization, with the top issues and recent signal changes across SQL, PostgreSQL and Cosmos DB
Estate inventoryA single inventory of supported Azure and Fabric databases, with their issues and suggestions
Performance monitoringNear real-time CPU, memory and storage trends, aggregated across the estate and per resource, plus normalized RU and throttled requests for Cosmos DB
Security postureFindings such as public network access, missing private endpoints, Microsoft Entra authentication, audit logging and customer-managed keys
InvestigationThe ability to drill from any finding into the affected resource, real-time dashboards and the tools you already use
New in general availability: Bulk performance monitoring enablement

Monitoring a large estate shouldn't mean configuring it one database at a time. You can now turn on performance monitoring at scale from the Estate view. Select multiple resources and enable performance monitoring data collection for all of them in one step.

  • Start from your inventory. Turn on monitoring in the same place you review your databases, without switching to another portal or tool.
  • Cover more of your estate, faster. Extend monitoring coverage across hundreds of databases without repeating setup for each one.
  • Go from setup to insight. Once data collection is on, monitored resources show up in Performance Monitoring and real-time dashboards.

 

New in general availability: Optimization insights

Optimization now sits alongside security and performance in Overview and Estate. It highlights:

  • Resources with a migration assessment ready
  • License model opportunities, such as pay-as-you-go
  • SQL Server instances that aren't reporting usage
Now generally available: Real-time dashboards

Real-time dashboards for Microsoft SQL, Azure Database for PostgreSQL and Azure Cosmos DB move from preview to general availability.

Now generally available: VS Code and SSMS entry points

DBAs work in SSMS, and developers work in VS Code. You can now open Database Hub from SSMS and from the Microsoft and MSSQL extensions for VS Code. You land in the same estate view, with the resources you were working on.

SSMS
VS Code
Now generally available: Database Hub CLI skill

Ask about estate inventory, health, performance and security posture from GitHub Copilot CLI, VS Code Copilot, Claude Code or Cursor. Get the Database Hub CLI skill from skills-for-fabric, or install it with one command:

skills-for-fabric --skill databasehub-cli

Then try asking, "How is my database estate doing?" or "Which databases need attention this week?"

In preview

Public preview: Investigate your estate with Copilot

Ask questions about your databases in natural language and get answers grounded in Database Hub data. Explore trends, understand issues and suggestions, and follow up on specific resources. Try prompts such as:

  • "What changed in my databases?"
  • "Which resource should I investigate next?"
  • "Which security findings should I address first?"
Public preview: Database Agents

Database Agents act as an extra set of eyes on your estate. An agent watches the databases you choose and stays quiet while they're healthy. When something needs your judgment, it raises an issue with supporting evidence and a recommendation. You stay in control: the agent brings the issue to you, and you decide what happens next.

Start with the overall finding or select Analyze on a single query to get recommendations for that query. From there, keep investigating with Copilot or go deeper in SSMS.

Database Hub is where you see the bigger picture. The database agent alerts you before your users notice.

Public preview: Alerts for Azure SQL Database

Create alerts from built-in templates or performance charts for one database or many. Alerts can send a Microsoft Teams message or start a Power Automate flow. They're powered by Fabric Activator.

 

Preview: Performance monitoring for SQL Server on Azure VMs

Review SQL Server on Azure Virtual Machines in the same Performance Monitoring experience as the rest of your estate.

What's next

More skills are on the way, including SQL performance monitoring, Cosmos DB performance monitoring and migration skills.

Get started today

Read more about Database Hub

Database Hub in Fabric: Now in Public Preview -Turn Database Signals into Guided Action | Microsoft Community Hub

Public Preview: Performance monitoring for Azure SQL in Database Hub | Microsoft Community Hub

A Single View of Your PostgreSQL Estate: Database Hub in Public Preview | Microsoft Community Hub

Make Estate yours: Focus on the databases and issues you own in Database Hub | Microsoft Community Hub

Public Preview: Alerts for Azure SQL Database in Database Hub, powered by Fabric Activator | Microsoft Community Hub

Managing security with Database Hub in Fabric: From signals to action | Microsoft Community Hub

Database watcher for Azure SQL is retiring: simplify your monitoring with Database Hub | Microsoft Community Hub

Ask your database estate a question: Copilot in Database Hub is now in public preview | Microsoft Community Hub

 

 

Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

episode 541 - which ai assistant should you actually trust w/ david pawlan

1 Share

if you want to check out all the things ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠torc.dev⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ has going on head to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠linktr.ee/taylordesseyn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ for more information on how to get plugged in!





Download audio: https://episodes.captivate.fm/episode/251451f5-8fd3-4be8-9145-d4e3459f912f.mp3
Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories