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.

---

## 1 Search-Driven Applications in .NET with Azure AI Search, Cosmos DB, and Vector Embeddings

Search used to mean matching words in a textbox against words in a database or index. That model still matters, especially for exact part numbers, SKU codes, legal terms, and named entities. But modern search-driven applications need more than keyword lookup. Users now ask natural language questions, describe intent vaguely, upload documents, compare products, and expect the system to understand meaning.

This article covers the foundation and architecture for building search-driven applications in .NET using Azure AI Search, Azure Cosmos DB for NoSQL, and vector embeddings. The focus is practical: how to think about the architecture, where each service fits, how vector data should be stored, and what trade-offs matter before writing production code. The requested scope is sections 1, 2, and 3 from the supplied outline.

### 1.1 From Lexical to Semantic: The Paradigm Shift

Traditional search engines are built around lexical retrieval. They index terms, normalize text, apply analyzers, and rank results based on how well query terms match indexed terms. This works well when users know the right words to type.

While creating a workflow system with the Microsoft Agents SDK, I encountered the following error message when testing my workflow:

System.InvalidOperationException: Cannot use a Workflow that is
already owned by another runner or parent workflow.
   at Microsoft.Agents.AI.Workflows.Workflow.TakeOwnership(...)
   at InProcessRunnerContext..ctor(...)
   at InProcessRunner.CreateTopLevelRunner(...)

It's cryptic if you haven't seen it before. But once you understand the ownership model, the fix is straightforward.

What's actually happening

.NET workflow runtimes treat workflow instances as stateful, non-reentrant objects. When a runner picks up a workflow, it takes exclusive ownership of that instance. No other runner — and no parent workflow — is allowed to touch it while that ownership is held.

This is by design. Workflows accumulate state as they execute, and allowing two runners to share that state simultaneously would corrupt it. The runtime enforces ownership as a hard constraint, not a soft lock.

The problem almost always has the same root cause: the workflow is registered as a singleton in the dependency injection container, and two requests arrive before the first one finishes. Both try to take ownership of the same instance — and one of them loses.

Why singletons cause this

When we call AddWorkflow<MyWorkflow>(key) without specifying a lifetime, the SDK often defaults to a keyed singleton. That feels sensible — why spin up a new object every time? But "singleton" means every call shares the same instance. Under any real load, concurrent requests will collide.

The stack trace in our exception confirms this: InProcessRunner.CreateTopLevelRunner calls TakeOwnership, which checks whether the instance is already claimed. It is, so it throws.

Three ways to fix it

1. Create a new instance per run (the simplest fix)

The most direct solution is to stop reusing a single instance. Instead, resolve or construct a fresh workflow object each time a run begins.

Before — singleton:

After — transient:

2. Use a factory pattern

If your workflow needs runtime parameters or non-trivial construction logic, a factory keeps things clean:

3. Check ownership timeouts for persisted workflows

If you're using durable/persisted workflows (backed by a database or checkpoint store), the ownership model extends across process boundaries. A previous run may have claimed ownership and crashed without releasing it — leaving the instance locked until the ownership lease expires.

In that case, check two things: whether another process is still actively holding the workflow, and whether your ownership timeout is long enough for your longest-running step. If timeouts are too short, a slow step will lose its lease mid-execution, and the next runner will see the same collision.

Quick checklist

• Change singleton registrations to transient for workflows that run concurrently
• Never share a workflow instance across requests — one instance, one run
• For persisted workflows, check that no other process holds ownership before retrying
• Tune ownership lease duration to exceed your longest step's expected runtime
• If sub-workflows are involved, ensure the parent passes the correct ownership signoff token

The ownership model isn't a bug — it's the runtime protecting you from state corruption under concurrency. Once you stop treating workflows like stateless services and give each run its own instance, the exception goes away and everything works as intended.

More information

Microsoft Agent Framework Workflows | Microsoft Learn