Here’s what “easier” means

Your SSIS packages still pay the bills. They’ve earned that. The orchestration logic, the error handling, the parameter discipline, the framework patterns you’ve layered on over the years – that’s not legacy debt. That’s working software running mission-critical loads.

What you’ve also been carrying is the sense that the platform conversation has moved past them. ADF, then Synapse, now Fabric. Every keynote a new abstraction. Every analyst report a new mandate. And every time you’ve asked “what about the SSIS packages already in production,” the answer has been some version of “rewrite everything.”

That answer never sat right. You’ve known it doesn’t have to be either-or. Most enterprise data estates are not greenfield. The honest path forward is one that respects the working software while making the platform move possible.

Last month at FabCon Atlanta, Microsoft announced something that finally moves in that direction. The Invoke SSIS Package activity, currently in preview, lets a Fabric Data Factory pipeline execute an existing .dtsx package directly.

No rewrite.
No Azure-SSIS Integration Runtime to provision and manage.
Your SSIS logic runs natively inside the Fabric orchestration layer.

That’s a real shift. For the first time, “lift and shift to Fabric” is a sentence with technical substance behind it for SSIS shops, not just slideware.

But before anyone bakes this into a 2026 roadmap, the preview status matters.

Packages and execution logs live in OneLake. The activity exposes the Connection Managers and Property Overrides tabs you’d expect, so connection strings and credentials can be set dynamically at runtime via expressions, pipeline parameters, or system variables. What’s deliberately less clear in Microsoft’s announcement is exactly which connectivity scenarios work today versus which are coming. The “what’s next” section calls out expanded package sources, on-premises and private network connectivity, and custom or third-party component support as forthcoming capabilities rolling out through a series of private previews. That language tells you where the current gaps are without specifying every one.

So the migration conversation does not end with “we’ll just use the Invoke SSIS Package activity.” It changes shape. The new questions are:

Which of your packages run cleanly against the current preview, and which depend on capabilities still being rolled out?

What’s the design pattern for hybrid orchestration — some pipelines invoking SSIS packages in Fabric, others still calling Azure-SSIS IR, others rebuilt as native Fabric pipelines?

When does the preview close enough gaps that retiring Azure-SSIS IR becomes a serious conversation?

What does Git integration, monitoring, and operational telemetry look like across that hybrid?

These are not blocking questions. They are design questions. The kind senior practitioners are good at, given clear information about what the platform actually does.

Software engineering solved the “how do I learn a new platform in a week without breaking production” problem years ago. Data integration mostly didn’t. The result has been twenty years of “burn a weekend reading docs, ship pilot project, hope it scales.” We can do better than that.

On 19 May, I’m running a full day on Fabric Data Factory. Live, online. We’ll work through what carries over from ADF, what doesn’t, the new Invoke SSIS Package activity and its current preview limits, the design patterns that survive the move, and the operational shape of running hybrid orchestration. Lecture and demo. No setup tax, no exercises, just a full day of getting senior practitioners to a working mental model.

If you’ve shipped pipelines in SSIS or ADF and you’re staring down a Fabric mandate, that day is built for you.

Register for A Day of Fabric Data Factory, 19 May 2026 →

Registration closes 16 May.

Microsoft released the "Windows Subsystem for Linux" in 2016, adding an optional Linux environment into every operating system since Windows 10. But now an open source developer has brought Linux to Windows 95, Windows 98, and Windows Me, reports the blog It's FOSS, "with Linux kernel 6.19 running alongside the Windows 9x kernel, letting both operate on the same machine at the same time." A virtual device driver handles initialization, loads the kernel off disk and manages the event loop for page faults and syscalls. Since Win9x lacks the right interrupt table support for the standard Linux syscall interrupt, WSL9x reroutes those calls through the fault handler instead. Rounding it all out is wsl.com, a small 16-bit DOS program that pipes the terminal output from Linux back to whatever MS-DOS prompt window you ran it from. The end result is that WSL9x requires no hardware virtualization, and can run on hardware as old as the i486, the article points out. On Mastodon the developer says they "really got this one in right under the wire, before they start removing 486 support from Linux." The source code for WSL9x is released under the GPL-3 license, and was "proudly written without AI."

Read more of this story at Slashdot.

Researchers at the University of Missouri-Kansas City and the University of Arizona say that between 2005 and 2019, the number of words we speak out loud to another human being fell by nearly 28 percent. And that has likely only gotten worse following the pandemic.

The researchers actually counted the number of words we were speaking on average (16,632 in 2005). They looked at data from 22 studies in which over 2,000 people recorded audio of their daily lives. Over time, as ordering through apps became the norm, texting increased, and our lives became increasingly online, they found that number had dropped dramatically. By 2019, we were onl …

Read the full story at The Verge.

Maine Gov. Janet Mills vetoed a bill that would have imposed the nation's first statewide moratorium on new data centers, saying she supported the idea in principle but would not block a major redevelopment project tied to jobs and local investment. Instead, she said she will create a council to study data centers' effects while also signing a separate measure to deny them certain state tax incentives. Politico reports: "After prior redevelopment efforts failed, the Town of Jay worked for two years on a $550 million data center redevelopment project to finally bring jobs and investment back to the mill site," Mills wrote, adding that she would issue an executive order establishing a council to examine the impact of data centers in Maine. The legislation would have made Maine the first state to block the construction of new data centers, as both political parties grapple with how voters view them ahead of the midterm elections. In a statement accompanying the letter, the governor said she had signed a separate bill that would prohibit data center projects from receiving Maine's business development tax incentive programs

Read more of this story at Slashdot.

Global Cloud & AI Community | Microsoft Tech Community | April 2026 | 12 min read

 

A candid conversation for cloud & AI professionals, learners, and curious minds navigating the most transformative shift in the history of technology.

Let's be honest with each other for a moment. Every week, a new AI tool drops. Every month, a new model breaks last month's benchmark. And somewhere in the back of your mind maybe while you're scrolling LinkedIn, or sitting through a product demo a quiet question surfaces: 

Am I keeping up? Will my skills still matter?

You're not alone in asking that. This blog is our attempt to answer it  not with buzzwords, but with real, actionable thinking for anyone in our community who wants to stay sharp, stay relevant, and actually thrive in what's coming next.

🧠1.Understand what AI actually changes (and what it doesn't)

Before we talk about up skilling, let's get grounded. AI is not a magic box that replaces people it's a force multiplier. It amplifies the capabilities of those who know how to work with it, and creates friction for those who ignore it.

Here's the reality: AI is already excellent at repetitive cognitive tasks summarizing documents, writing boilerplate code, drafting emails, classifying data. Where it still needs you is in judgment, context, ethics, creativity, and relationship. Your value in an AI-driven world is not just what you know it's how you think.

As cloud and technology professionals, we're actually in a privileged position. We sit at the intersection of infrastructure, security, and intelligence. The question is whether we lead the AI adoption curve or watch it from the sideline.

AI won't replace you but a professional who knows how to use AI effectively might. The gap between those two scenarios is exactly what this blog is about.

📚2.Commit to Continuous, Deliberate Learning

There's a difference between passive learning watching a YouTube video, skimming an article  and deliberate learning, which is structured, goal-oriented, and applied. In a fast-moving field, the latter is the only kind that compounds.

Microsoft Learn remains one of the most under utilized resources in our community. Whether you're exploring AI Fundamentals (AI-900), the new AI Engineer path (AI-102), or deepening cloud security knowledge across AZ-500 and SC-200 there is a structured learning path built for your exact role.

But don't stop there. Build a personal learning system: set a weekly learning goal, track it, and share it publicly in the community. Accountability accelerates everything.

Where to Start Right Now:

Microsoft Learn's AI Skills Challenge · Microsoft Applied Skills assessments · LinkedIn Learning paths · GitHub Copilot hands-on labs

Microsoft Learn | AI-900 Fundamentals | AI-102 Engineer | Applied Skills

🔧3.Get Hands-On-Not Just Certified

Certifications matter. They signal credibility, demonstrate commitment, and open doors. But in the AI era, certifications alone are table stakes. What separates the top 10% is what you've actually built.

Spin up a free Azure subscription. Deploy a Copilot Studio bot. Connect Microsoft Sentinel to a log source and write a KQL query. Build an AI document processing pipeline using Azure AI Services. None of this requires a budget  it requires curiosity and a weekend afternoon.

The portfolio of projects you build tells your story more convincingly than any certificate. Share it on GitHub. Write about it here on the Tech Community. Turn your experiments into blog posts that help others.

Practical Challenge for This Week Pick one Microsoft AI service you've never touched

Azure OpenAI, AI Content Safety, Copilot Studio, or Semantic Kernel and spend 2 hours building something with it. Then share what you learned.

Azure OpenAI | Copilot Studio | Semantic Kernel | Azure AI Foundry

"The future belongs to those who learn more skills and combine them in creative ways." — Robert Greene

🤝4.Invest in Your Human Skills -They're Your Moat

Here's something the AI hype cycle tends to underemphasize: the skills AI is worst at are the ones that will become most valuable. Critical thinking. Ethical reasoning. Communication. The ability to ask the right question before you ask the AI anything at all.

As AI handles more execution, the demand for people who can define the problem, design the solution, and manage stakeholder expectations will only grow. In cloud security roles especially where decisions about data sovereignty, compliance, and Zero Trust architecture carry real organisational risk ,human judgment is irreplaceable.

Practice explaining complex technical concepts in plain language. Learn to present to non-technical stakeholders. Volunteer to mentor someone more junior than you. These human investments compound quietly and become enormously valuable.

Skills That AI Can't Automate Away

Strategic thinking · Executive communication · Ethical judgment · Cross-functional collaboration · Mentoring · Stakeholder empathy

🌐5.Build and Nurture Your Professional Network

In an AI-driven world, what you know is increasingly commoditized large language models can retrieve most factual knowledge faster than any human. What can't be commoditised is who you know, who knows you, and the trust you've built over time.

Our Tech community is one of the most direct opportunities you have to do exactly that. Write a blog post here even an imperfect one. Answer someone's question in the forums. Show up to a virtual event. Engage with others' content thoughtfully.

The professionals who thrive in the next decade will be those who've built a reputation as generous contributors in their communities. Reputation is a career asset that compounds over years and is almost impossible to replicate quickly.

Community Actions That Build Your BrandP

Publish a technical blog post · Answer questions in Tech Community forums · Speak at a User Group · Contribute to a Microsoft-related open source project

🧭6.Develop an AI Mindset -Not Just AI Skills

The deepest competitive advantage you can cultivate isn't knowing the latest AI tool. It's developing a mindset that's comfortable with rapid change, experimentation, and uncertainty. This is what separates professionals who adapt from those who get left behind not raw technical knowledge, but adaptability itself.

Adopt a habit of weekly technology scouting. Subscribe to the Microsoft AI blog. Read Microsoft Research papers. Follow key voices at Microsoft and in the broader AI ecosystem. Curate a shortlist of three people whose thinking you respect and read everything they write.

Most importantly: stay curious. The professionals most at risk aren't the ones who don't know AI it's the ones who stopped being curious. Curiosity is renewable. Expertise built from it is durable. In a world of AI-generated content, your genuine perspective and lived experience are irreplaceable signals.

The AI Mindset in Practice

Experiment weekly with new AI tools · Read broadly across disciplines · Embrace being a beginner again · Share your failures alongside your wins

Microsoft AI Blog | Microsoft Research | Build-With-AI events | AI Skilling Week

Final Thought: The competitive edge is a daily practice

Relevance in an AI-driven world isn't a destination you arrive at  it's a rhythm you maintain. It's the 30 minutes you spend learning something new on  every day. It's the blog post you almost didn't write. It's the conversation you started in the community forum that led somewhere unexpected.

We built this community so that none of us has to navigate this alone. Share this post with a colleague who's wrestling with these questions. Drop a comment with what you're working on. Let's build something together.

---