The Hard Part Isn’t Adding Anymore

I caught myself last week with eleven browser tabs open, three half-built automations, a new Planner board nobody asked for, and a Teams channel I’d spun up that morning and already forgotten the purpose of. None of it was hard to create. That was the problem. Every one of those things took me about ninety seconds, and ninety seconds is now the entire cost of bringing something new into existence.

For most of my working life, the brake on doing more was effort. You wanted a new report, a new process, a new client deliverable — and the friction of actually building it slowed you down enough to ask whether it was worth it. That friction is mostly gone. Copilot drafts the document, the deck, the email sequence. Power Automate wires the workflow. The wall that used to stop me from acting on every passing idea has quietly come down.

Speed without judgement is just mess

I’ll be honest about the wiring in my own head. I’m wired to react. A thought lands, I want to act on it immediately, and for years that instinct ran straight into the resistance of having to do the work by hand. The work was the filter. It forced a pause.

Now there’s no pause. The reaction and the execution have collapsed into the same moment. I think “we should have a dashboard for that” and Copilot in Excel has one in front of me before the idea’s even finished forming. Multiply that across a week and you don’t get a sharper business. You get a cluttered one. More dashboards nobody reads. More channels nobody checks. More automations quietly firing into inboxes that have stopped paying attention.

The skill that used to matter was production — the ability to make the thing. That’s not scarce anymore. Anyone with a Copilot licence can produce. What’s scarce now is the judgement to know which of the ten things you could build is the one that actually matters, and the discipline to let the other nine die.

Taste is the work now

I keep coming back to the word taste, because I can’t find a better one. It’s the ability to look at everything you’re capable of generating and recognise what’s worth keeping. It’s hearing the difference between a real signal and noise dressed up to look like progress. And it’s having the spine to cut — to delete the document, kill the channel, switch off the automation — even though it cost you almost nothing to make and feels wasteful to throw away.

This is uncomfortable, especially for those of us who measure ourselves by output. Cutting feels like the opposite of productivity. But a business that adds endlessly and never subtracts doesn’t get faster. It gets heavier. Every new thing you create has a maintenance cost, an attention cost, a “what was this for again?” cost that lands months later. The Loop pages multiply. The SharePoint sites pile up. The thing you built in ninety seconds takes a year to quietly rot in front of everyone.

So I’ve started running my week the other way around. Instead of asking Copilot what else I could build, I ask it what I should stop. I’ll point it at a Teams channel and ask for a summary of the last month — and if the honest answer is “three automated posts and no human replies,” that’s my cue to shut it down. I use Copilot to find the dead weight, not just to make more.

The momentum problem

Here’s the part I want to be straight about, because it’s where I think a lot of us are stuck. You can feel that your best work is still in front of you. The ambition is real. But the momentum you’re chasing won’t arrive while the business is carrying this much weight. Every unfinished idea, every half-used tool, every process you bolted on and never removed is drag. You can’t accelerate something this loaded, no matter how fast you’re able to add to it.

The temptation, when you feel slow, is to add more — a new tool, a new system, a new initiative to fix the sluggishness. That instinct is exactly backwards. The way through isn’t more production. It’s subtraction. The lightness comes from what you’re willing to remove.

It’s never been easier to make something. Which means the rare, valuable, genuinely hard skill is no longer making — it’s choosing. Less, but the right less. That’s the whole game now.

GAIN: Knowing What to Hand to AI and What to Hold Onto

A while back I caught myself spending a Saturday morning copying figures into a spreadsheet by hand. Forty minutes in, it landed on me — Copilot could have done this while I made a coffee. I wasn’t being thorough. I was being slow. And when the person at the top moves slowly, everything behind them backs up too.

That morning is why I keep coming back to a simple way of sorting the work in front of me: what to pass over, what to speed up, what to build alongside the machine, and what I should never let go of. Four buckets. GAIN.

Pass over the work that doesn’t need you

Most of us hold on to tasks out of pure habit. The first draft. The long document that needs boiling down. The background reading before a client call. None of that needs your judgement — it just needs doing. So let it be done. I’ll ask Copilot in Word to condense a forty-page proposal, or have it pull the recurring themes out of a month of client emails in Outlook. I’m not after ideas. I’m after a finished job. Once you start looking, the size of this pile is genuinely surprising.

Speed up the things that already work

Every business runs on small, repeatable steps. An enquiry arrives, someone qualifies it, someone books the meeting, someone sends the follow-up. You’re not reinventing that — you’re stripping out the waiting in between. With Power Automate sitting under Copilot, a new lead can be sorted, routed, and have a meeting request out the door before anyone’s even read it. Two hours back a week, every week, for as long as the doors are open. That compounds in a way that’s easy to dismiss when you’re staring at the setup.

Build something you couldn’t make alone

This is the part people skip past. The real value isn’t AI standing in for you — it’s the two of you producing something neither would on its own. I’ll have Copilot take ideas I’ve already worked through, connect them in ways I hadn’t spotted, and hand them back in a different shape. Sometimes I’ll drop a Loop page of rough notes and let it pull the thread together while I’m out of the office. I come back and I’m editing, not starting from a blank page. Minutes of shaping instead of hours of grinding. You shift from making the thing to sharpening it — and that’s a far better use of your attention.

Keep what only you can do

Not everything belongs on these piles, and pretending otherwise is how people lose the plot. Taste can’t be handed over — it’s learned, never taught, and certainly never prompted. Vision stays yours, because the machine has no idea what your clients will want next year. And care — actually feeling something for the work and the people on the other end of it — that’s the whole point of doing any of this. Copilot can draft the message; it can’t mean it. Guard those three closely.

The aim was never to turn yourself into the software. It’s to clear away everything else so there’s more room for the part of the job that’s unmistakably yours. I’m curious how far that line shifts over the next year — but those last few things, I don’t think they move at all.

Is Microsoft Losing Its Memory?

Over the last few weeks I’ve had more than a few conversations that have nothing to do with technology and everything to do with people.

The topic? Microsoft.

Not the products. Not Copilot. Not Azure. The company itself.

With another round of layoffs and a steady stream of experienced employees announcing their departure, many people are starting to ask the same question: Is Microsoft becoming a completely different company? And if so, is that a good thing?

It’s a fair question because a lot of the people leaving aren’t newcomers. They’re the people who have spent years, sometimes decades, building products, relationships, culture and institutional knowledge. They know why certain decisions were made. They remember what worked, what failed, and what lessons were learned along the way.

When that experience walks out the door, something goes with it.

Every Generation Reinvents the Company

One thing I’ve learned from watching Microsoft over many years is that the company is constantly reinventing itself.

The Microsoft that built Windows isn’t the same Microsoft that built Azure.

The Microsoft that created Office isn’t the same Microsoft that now delivers Microsoft 365.

And the Microsoft that is investing heavily in Copilot and AI today is once again becoming something different.

In many ways that’s exactly why the company has survived when so many technology giants have faded away. It has shown an ability to change direction when the market changes.

The challenge is that reinvention often comes with a cost. New people bring new ideas, new priorities and new ways of working. That’s healthy. But if too much historical knowledge disappears at the same time, organisations can find themselves solving problems that were already solved years ago.

Sometimes experience isn’t about knowing what to build. It’s about knowing what not to build.

The Hidden Value of Institutional Knowledge

When people think about layoffs, they often focus on roles and headcount.

What doesn’t get measured so easily is context.

Every organisation has unwritten knowledge. The things that never make it into documentation. The conversations that explain why a process exists. The lessons learned after a customer escalation. The accumulated understanding of how products, teams and markets really work.

Ironically, this is exactly what many businesses are now trying to capture with AI.

When organisations deploy Microsoft 365 Copilot, one of the first discoveries is that their knowledge is scattered everywhere. Some of it lives in SharePoint. Some is hidden in Teams conversations. Some is trapped inside Outlook mailboxes. And some only exists inside the heads of experienced employees.

When those employees leave, that knowledge often leaves with them.

That’s why I believe one of the greatest values of Microsoft 365 isn’t just productivity. It’s preserving organisational memory. Every Teams meeting transcript, every shared document, every Copilot-assisted summary creates a record that can help future employees understand the context behind decisions.

Technology can help capture knowledge, but it can’t replace the judgement that created it in the first place.

Could This Actually Make Microsoft Stronger?

The other side of the argument is equally compelling.

Large organisations can become attached to the way things have always been done. Fresh perspectives can challenge assumptions. New leaders can move faster because they’re not carrying the weight of past decisions.

You can certainly argue that Microsoft’s rapid shift towards cloud computing and now AI required new thinking that may have been difficult inside a company built around legacy business models.

A business that never changes eventually becomes irrelevant.

The risk isn’t change itself. The risk is changing so quickly that you forget what made you successful in the first place.

There’s a balance to be found between respecting experience and embracing new ideas.

What I’ll Be Watching

As Microsoft pushes deeper into the AI era, I think the real test won’t be how many people leave or how many new people join.

The test will be whether the company can preserve the culture, engineering discipline and customer focus that helped build its reputation while simultaneously creating something new.

Most successful organisations stand on two foundations: experience and innovation.

Lose innovation and you fall behind.

Lose experience and you repeat old mistakes.

The companies that thrive find a way to keep both.

Microsoft has reinvented itself many times before. The question now is whether this latest transformation strengthens the foundations of the company or slowly erodes the knowledge that helped make it one of the most influential technology organisations in the world.

Creating a Digital Twin of Your Business

When most people hear “digital twin”, they picture an engineer running a virtual copy of a jet engine, or watching a simulated factory floor hum along on a screen. It sounds like something built for heavy industry, a long way from a business that runs on email, spreadsheets and the occasional frantic search through old files. I’ve come to think the idea fits an ordinary organisation just as well — and that most of us are far closer to having one than we’d assume. The raw material is already sitting there. We’ve just never thought of it in those terms.

A digital twin of a business isn’t a 3D model. It’s a living representation of how your organisation actually thinks: the decisions it has made, the reasons behind them, the way a job quietly moves from one person to the next. That knowledge already exists. The problem is that it’s scattered. Some of it sits in SharePoint, some in a Teams thread nobody has opened in a year, some buried in a colleague’s sent items — and an uncomfortable amount lives only inside one person’s head.

You already own the knowledge

A while back I watched someone spend half a morning answering a question their business had already answered twice. The work existed. It simply couldn’t be found quickly enough, so they built it again from nothing. That’s the everyday cost of not having a twin you can talk to. You’re not short of information. You’re short of a way to ask your own business what it already knows.

This is where Copilot starts to shift things. Connected across your Microsoft 365 tenant, it lets you put a question in plain language and pulls the thread together for you. Ask why a particular client moved onto a different plan, and Copilot can surface the Outlook email where it was decided, the meeting where it was thrashed out, and the document that recorded the outcome. A new staff member can ask it how something is normally done and get an answer drawn from real history, not folklore. You stop hunting for a file and start interrogating your own past.

The twin is only as good as what you feed it

This is where most businesses come undone. If a decision gets made on a phone call and never written down, the twin can’t see it. If the reasoning lives only in someone’s memory, it isn’t in the model. So the habit worth building is unglamorous but powerful: put decisions somewhere Copilot can reach. Keep the Teams meeting recap instead of letting it disappear. Write the why into the document, not just the what. Treat a SharePoint page or a Loop component as the place your thinking genuinely lives, rather than a tidy-up job for later.

None of that is technical work. It’s a discipline — choosing to treat your own knowledge as something worth keeping, instead of something you’ll cobble back together under pressure when you next need it.

What it actually buys you

I don’t think the goal is a perfect replica. No model captures everything, and you wouldn’t want one that tried. But a business that can answer its own questions — one that remembers why it did things — moves faster and argues less. It brings new people up to speed sooner. It stops relitigating decisions that were settled months ago.

The pieces are already sitting in your tenant, waiting to be connected. What I’m watching now is which businesses bother to feed the twin, and which keep solving the same problem every Tuesday morning, none the wiser for having solved it before.

The AI Toolkit Monetization Strategy: Building Enterprise Value with Microsoft Technologies

I’ll start with something that won’t win me any friends at the next AI meetup: owning the cleverest AI tool in the room won’t make you a cent. Not the model, not the agent, not the prompt you spent a weekend perfecting. I’ve watched a lot of people fall in love with the technology and then wonder why the invoices aren’t getting any bigger. The uncomfortable truth is that nobody pays for tools. They pay for problems disappearing.

Think about a carpenter for a moment. A carpenter doesn’t get wealthy selling you a single hammer off the back of the ute. They get paid because they walk onto a site, look at a house that needs building or a roof that’s letting the rain in, and they know exactly which tool to reach for and when. The hammer matters, but only because of the hand holding it and the job it’s pointed at. That’s the mindset I think anyone serious about AI needs to adopt — and if your organisation already lives inside the Microsoft cloud, you’ve quietly been handed a very good toolkit. Most people just haven’t worked out how to pick it up.

The hammer: Copilot and Azure OpenAI

The language model is your hammer. It’s the tool you swing by hand, and it’s genuinely powerful — but it does what you tell it, no more. In the Microsoft world that’s Microsoft Copilot sitting across your Outlook, Word and Teams, with Azure OpenAI underneath when you need to build something bespoke.

Here’s where most people get it wrong: they treat Copilot like a fancier search box. They type a vague half-question, get a vague half-answer, and conclude the whole thing is overhyped. The people getting real value approach it with a bit of discipline. The way I think about it is four steps — mission, ask, parameters, shape.

Start with the mission: the business outcome, not the chore. Don’t ask Copilot to “find me some leads.” Tell it you need thirty new enterprise clients this quarter to hit a revenue target. Then comes the ask — one sharp, specific request, like pulling together forty qualified IT directors in healthcare with their contact details. Then parameters — the context and the guardrails. This is where Copilot in Microsoft 365 earns its keep, because you can point it straight at the files in your SharePoint or OneDrive so it’s reasoning over your data, not a guess about the world. A tip I lean on constantly: dictate your context rather than typing it. The voice option in Copilot lets you talk through the background in thirty seconds, and you talk far faster than you type. Finally, shape — tell it the format you want. A clean table, a CSV you can drop into Excel, a tight bulleted summary. Stop reformatting things by hand like it’s 2015.

The screwdriver: Power Automate

A hammer needs a fresh swing every single time. The moment you find yourself doing the same AI-assisted task over and over, you’ve outgrown it. That’s when you reach for the screwdriver — automation — and in the Microsoft stack that’s Power Automate with AI Builder doing the heavy lifting.

The shift here is subtle but enormous. Instead of opening Copilot every morning to run the same prompt, you build a flow once and let it run on a schedule or off a trigger, quietly, in the cloud, forever.

Not everything deserves a flow, though, and this is where people burn weeks they’ll never get back. I run three quick tests before building anything. Is it repetitive — happening at least weekly, ideally daily? Is it rule-based, with predictable inputs and a predictable result? And does it actually pay back — does the time saved over a year dwarf the time spent building it? Don’t spend sixty hours constructing a flow that rescues someone two minutes a week. That’s not automation, that’s a hobby.

A example I like: a sales call recording lands in a Teams channel. Power Automate sees it, AI Builder pulls the transcript, reads the sentiment, drops the action items straight into Dynamics 365, and posts a tidy weekly summary back into the leadership channel in Teams. Nobody touched it. That’s the screwdriver doing its job.

The power drill: Copilot Studio

Then there are the jobs where you don’t want to define the steps at all — you just want the outcome. That’s the power drill, and Microsoft’s answer is Copilot Studio, where you build agents that handle whole processes on their own.

With the hammer and the screwdriver, you’re still drawing the map. With an agent, you describe the destination and let it find its own way through the subsystems. The trick to doing this without disaster is what I’d call staying on the loop rather than in it. Pick a genuinely meaty workflow — vendor onboarding end to end, say, from reading the invoice email, to cross-checking your Dataverse tables, to running compliance, to setting up billing. Then, and this is the hard part, don’t keep grabbing the wheel. Let it run.

Two habits make this safe. First, have agents check each other — a builder agent in Copilot Studio writes a script, and a separate reviewing agent picks it apart for security gaps before anything reaches a human. Second, watch for drift. An agent grinding away over hours or days can slowly lose the plot, so your role becomes the manager who inspects, resets the context when it wanders, and keeps it pointed at the goal.

The orchestrator gets paid

Here’s the part that actually moves the money. Owning these three tools doesn’t make you rich. Conducting them does. The orchestrator is the one who looks at a bleaking supply chain or a drowning support desk and reaches across the whole Microsoft AI toolkit — Copilot, Power Automate, Copilot Studio — to make the pain stop.

Your clients don’t lie awake wondering whether you used GPT-4o through Azure or a Copilot Studio agent. They lie awake about their costs. Solve that, and the technology underneath becomes a footnote. Problems are where the value lives.

So the real shift isn’t learning another tool. It’s moving from doing the work to directing it. Step back, find the problem worth solving, and orchestrate the kit you already own.

The Most Important Part of Productivity Is the Product

I had a conversation last week that’s stuck with me. Someone was describing their week — back-to-back meetings, an inbox wrestled down to zero, a colour-coded calendar that would make a project manager weep with joy. They were exhausted and, oddly, proud of it. So I asked a simple question: what did you actually make? Long pause. The honest answer was “not much.” A full week of motion, and almost nothing to show for it.

We’ve quietly redefined productivity to mean busyness. How fast you reply. How many minutes you squeeze from a day. How efficiently you move between tasks. But strip the word back and the heart of it isn’t the activity — it’s the product. The thing that exists now that didn’t exist on Monday morning. The proposal that’s written. The decision that’s made. The client problem that’s solved. Everything else is just noise around the signal. We measure the noise because it’s loud and easy to count. The signal is quieter, and it’s the only part that actually matters.

Motion is easy to measure. Output is the hard part.

The reason we drift toward efficiency is that it’s comfortable. You can count emails sent and meetings attended. You feel the satisfaction of a tidy inbox. But none of those are products — they’re scaffolding. I’ve watched people spend an entire afternoon “getting organised” and call it a good day’s work, when really they just rearranged the furniture. The week looked productive. Nothing was produced.

This is where I think Copilot changes the conversation, and not in the way the marketing suggests. The point isn’t that it makes you faster at the busywork. It’s that it takes the busywork off the table, so what’s left is the actual product. When I ask Copilot in Outlook to summarise a long thread and draft the reply, I haven’t saved twenty minutes — I’ve removed a task that was never the point. The reply was never my product. The thinking behind it was.

Spend the time you save on something worth showing.

That’s the part people miss. The danger isn’t that Copilot does the low-value work — it’s what you do with the gap it opens up. If Copilot pulls your meeting notes and action items together in Teams, and you spend that reclaimed hour clearing three more emails, you’ve efficiency-ed yourself in a circle. But if you use it to write the strategy document you’ve been avoiding, or to think properly about a client’s problem in Word with Copilot helping shape the argument, the tool has earned its place. Or you point Copilot at a messy spreadsheet in Excel, ask it what the numbers are really saying, and walk into the meeting with an answer instead of a pile of data. The output, not the speed, is the scorecard.

I’ve started asking myself a blunt question at the end of each day, and I’d suggest you try it. Not “was I busy?” — I’m always busy. The question is: what can I point to? What did I produce that someone else could pick up, use, or judge? Some days the answer is a single solid thing, and that beats a day filled with forty small tasks that vanish the moment they’re done.

Copilot has made me more honest about this, because once the friction is gone, you can’t hide behind it. The empty afternoon is exposed for what it is. That’s the real shift worth watching — not doing things faster, but finally being able to ask whether the thing was worth doing at all.

The Quiet Productivity Cost of Watching AI Work

I noticed something a few weeks back during a busy Friday afternoon. I’d asked Copilot in Word to pull together a draft summary of a long client document, and instead of moving on to the next thing on my list, I just sat there. Watching. Cursor blinking. Sentences slowly stitching themselves across the screen like I was waiting for a kettle to boil. It took me a good thirty seconds to realise I was, in effect, staring at a digital pot — and getting absolutely nothing else done while I did it.

That small moment has stuck with me. Because I don’t think I’m the only one doing it.

The watching trap

There’s a quiet productivity tax that nobody really warned us about with generative AI inside Microsoft 365. We’ve been told these tools save us hours. And they will — but only if we actually use those hours. The moment we anchor ourselves to the screen and watch Copilot draft a reply in Outlook, summarise a meeting recording in Teams, or build out a deck slide by slide in PowerPoint, we hand back every minute of the gain.

I think this happens because the output feels unfinished until it’s done. The brain treats it a bit like a conversation — and you don’t walk away from someone mid-sentence. But Copilot isn’t speaking to you. It’s working for you. And it doesn’t care whether you’re in the room.

The result is a strange new flavour of busywork. You look productive. You’re sitting at your desk, focused, eyes on the screen. But the actual output of your time is whatever Copilot was going to produce anyway. You’ve added nothing. You’ve just supervised a process that didn’t need supervising.

Why staring at it doesn’t help

The other problem with the watching habit is that it isn’t even useful. You can’t speed Copilot up by looking at it harder. You’re not catching errors in real time, because most of us don’t read carefully enough mid-generation to spot a problem — and you’ll review the final output once it’s done anyway. The watching is pure overhead.

Worse, it primes a passive mindset. When you sit and observe the machine doing the work, you start to mentally check out. The next task on your list feels heavier than it should. You lose the rhythm of context-switching that real knowledge work depends on. By the time the draft email or summary lands, you’ve already half-disengaged. So instead of pouncing on it, reviewing it sharply, and sending it on its way, you take another minute or two to gather yourself.

That’s two layers of cost. The time you spent watching, and the time it takes to mentally re-enter the work.

Treat Copilot like a colleague, not a performance

The shift I’ve had to make is treating Copilot the same way I’d treat anyone I’ve delegated something to. You don’t stand over a colleague’s shoulder while they write a document. You hand it off, you go do something else, and you come back to review when it’s ready.

So when I ask Copilot in Excel to analyse a dataset, I switch to my inbox and clear a few replies. When I have Copilot in Word drafting something substantial, I move into Teams and respond to chats. When a deck is being assembled in PowerPoint, I’m reviewing tomorrow’s calendar or skimming a SharePoint document I’d been putting off. The five or ten seconds of context-switch cost is well worth the two or three minutes I would have otherwise stared away.

The deeper habit, though, is queueing the work. I now line up several AI-assisted tasks at once. A summary running here, a draft being produced there, an analysis underway in another window. Copilot is happy to run in parallel across Microsoft 365. There’s no good reason to make those tasks sequential by tying each one to your eyeballs.

What I’m watching next

The thing I’m paying attention to from here is how teams handle this collectively. Because once AI is doing more of the small tasks across an organisation, the productivity ceiling stops being defined by what the tools can do and starts being defined by what their humans do while the tools work. The businesses that win the Copilot game won’t be the ones with the best prompts. They’ll be the ones whose people have stopped sitting and watching, and started filling that reclaimed time with thinking, deciding, and acting.

The technology is doing its part. The next move is ours.

TechWerks 30 – Comprehensive Recap & Best-Practice Guide

After hosting the recent Techwerks event in Melbourne, I go Copilot to put together this summary of the day as a reference to what the day is all about and hopefully demonstrate the value it provides by attending.

TechWerks 30 was a full-day, face-to-face Microsoft 365 deep-dive hosted by Robert Crane (CIAOPS) in Melbourne on 24 June 2026. This manual provides an in-depth recap of the major topics and hands-on sessions recorded during TechWerks 30, serving both as a post-event reference for attendees and a resource showcasing the unique value of these immersive training days to prospective participants. It synthesizes content from all four recorded sessions, focusing on key themes, tools, and takeaways while omitting any personal or sensitive information.

Executive Summary: TechWerks 30 offered a highly interactive, attendee-driven training experience in Microsoft 365 and related technologies. Instead of passively listening to pre-set slides, a small group of under 20 attendees actively shaped the agenda by voting on the topics they needed most. This approach ensured every session tackled real-world scenarios and pressing challenges that participants face in their day-to-day work, from managing cloud storage to bolstering security settings, and even exploring emerging features like Microsoft Copilot* and Copilot Co‑pilot’s new usage-based billing model. The event delivered practical demonstrations, live problem-solving, and best practices that participants could immediately apply in their own environments – producing numerous “Monday-morning” takeaways and clear business value.

Major Topics and Hands-On Activities

TechWerks 30 encompassed multiple major themes spanning the Microsoft 365 ecosystem, each addressed through interactive demonstrations and group discussions. Key topics included cloud collaboration best practices, security & identity management in M365, and the latest AI and product updates (with an emphasis on practical implications). Below we delve into each of these themes in detail, describing what was covered and highlighting the session’s live demos, best practices, and takeaways.

1. Collaboration & Cloud Data Management (OneDrive, SharePoint, & Teams)

OneDrive for Business & SharePoint Best Practices: A significant portion of the day was devoted to optimizing file storage and collaboration workflows in Microsoft 365, particularly OneDrive for Business (ODFB) and SharePoint Online. Many attendees still had questions on effectively using ODFB, highlighting that even seasoned users often seek clarity on fundamentals (a common scenario noted by the host).

**“Add to OneDrive” vs Syncing Document Libraries: One best-practice discussed was the use of OneDrive Shortcuts (the “Add shortcut to OneDrive” feature) instead of syncing entire SharePoint libraries. This approach offers key benefits: it saves local disk space and reduces sync complexity by letting users pick specific folders or libraries to access via their OneDrive, rather than syncing large libraries in full. Shortcuts also streamline collaboration by ensuring a single source of truth (no duplicate copies) and improving users’ day-to-day workflows through easier access to shared content. Participants learned how to create and manage these shortcuts and how they appear in their OneDrive, avoiding common issues with oversynchronization and orphaned local copies.
OneDrive Storage Management: The group addressed how to manage and increase OneDrive storage quotas. Attendees learned that Microsoft 365 tenants can raise the default ODFB storage from 1TB to 5TB per user for eligible plans. The manual review included step-by-step guidance (via the Microsoft 365 Admin Center and PowerShell commands) to adjust both default storage quotas and existing user quotas to 5 TB for all users – a valuable tip for growing businesses to avoid users hitting capacity limits. This discussion underscored the importance of proactive tenant capacity planning in cloud storage deployments.
**OneDrive Offline Access and File Sync: The latest OneDrive enhancements were highlighted, including the new Offline Mode for OneDrive Web. This upcoming feature (an extension of the Files On-Demand concept) allows users to mark files/folders in OneDrive web as “always available offline” – so they can continue working on cloud files in the browser even without internet, with changes syncing once reconnected. While offline web access was still rolling out in 2026, attendees appreciated how it narrows the gap between local and cloud storage and ensures business continuity during internet outages. The trainer contrasted this with the existing OneDrive Sync client (OneDrive.exe), which has long provided offline access by syncing files to local drives. The combination of these capabilities – traditional Sync for robust offline use, and the new Web offline mode for added flexibility – was discussed as part of a holistic file access strategy.
Real-World Troubleshooting Example – Excel & OneDrive: In the spirit of addressing real problems in real time, a participant’s recent issue was examined: Microsoft Excel crashing when saving files to a OneDrive Shared Library (via a shortcut). Rather than theoretical advice, the group diagnosed the issue interactively. Drawing on community and Microsoft knowledge, they discovered it was a known bug triggered by a recent patch (the May 2026 update) affecting Excel’s integration with OneDrive shortcuts. They discussed the official guidance that Microsoft provided (and any available workarounds), thereby reinforcing the day’s focus on immediate problem-solving. This example illustrated how TechWerks sessions deal with timely challenges and share the latest information on issues that matter to participants – in this case, confirming that Microsoft was aware of the bug and investigating, and that a fix or mitigation was on the way.

2. Security & Identity: Best Practices and Tools for Microsoft 365

Another core theme was securing Microsoft 365 environments. Attendees explored practical identity and access management strategies, with a particular focus on Conditional Access policies in Azure Active Directory (Entra ID) and baseline security configurations for small-to-medium businesses.

Conditional Access (CA) Policies – Implementation & Avoiding Pitfalls: The group walked through the process of setting up Conditional Access policies that enforce modern zero-trust principles in Microsoft 365. This included real-time demonstrations of creating CA policies to require multi-factor authentication (MFA) for users, block legacy authentication, and restrict logins from risky locations. A key best practice highlighted was to configure “named locations” (trusted geographic locations or IP ranges) in advance before enabling broad location-based blocking policies. This prevents an*“accidental lockout”* of all users – an easy mistake if an admin, for example, enables a blanket “block all sign-ins outside country X” rule without first defining country X as a trusted location. By applying this lesson, attendees learned how to tighten security without cutting off legitimate access to their cloud services.
Automating Best-Practice Security Setup: The session introduced tools to streamline the implementation of best-practice security baselines. Participants were shown a PowerShell-based “M365 Best Practice” script toolkit (commonly used by the CIAOPS community) that can automatically configure recommended security settings – including a baseline set of CA policies aligning with standards like the Australian Cyber Security Centre’s “Essential Eight” framework (ASD guidelines). Running these baseline scripts on a test tenant produced an immediate snapshot of the environment’s security posture, highlighting gaps and misconfigurations. Attendees were impressed by the results of a*“Tenant Posture”* script, which quickly identified areas for improvement (eliciting a “wow” from participants as it revealed areas of risk and potential enhancements).
Advanced Security & Compliance Topics: The group further discussed emerging security features and strategies. This included an overview of recent additions like Microsoft Entra ID improvements (for identity protection), and the importance of routine secure score reviews and policy audits to keep up with evolving threats. The interactive format allowed participants to ask specific security scenario questions (for example, how to handle specialized cases in conditional access, or ensuring privileged accounts remain accessible during emergencies). The emphasis was on practical steps that small and midsize organizations can implement immediately – such as enabling MFA for all users, using Conditional Access templates or “baseline” policies provided by Microsoft, and leveraging monitoring tools (like Secure Score and sign-in logs) to continuously track and improve tenant security. Participants left with clearer guidance on prioritizing critical security measures and confidence to apply these in their own environments.

3. Emerging Technologies & Microsoft 365 Updates

Although the primary focus was on attendee-requested core topics, TechWerks 30 also touched on a few of the latest Microsoft 365 updates and emerging tools around the time of the event:

Copilot Cowork & Usage-Based Billing: The event coincided with Microsoft’s general availability of Copilot Cowork – a new AI-driven**“agentic” assistant in Microsoft 365** capable of performing multi-step tasks, which was widely discussed at Microsoft Build 2026. The instructor provided an overview of Copilot Cowork’s capabilities and its new usage-based billing model, noting how this marks a shift in how AI features might be purchased. Attendees learned that beyond the standard M365 Copilot license (a flat per-user fee), using Cowork’s advanced autonomy features may incur consumption-based charges (“Copilot Credits”), and that IT admins must explicitly enable and configure Cowork’s pay-as-you-go billing by linking an Azure subscription to their tenant. It was noted that at launch, Cowork is opt-in (disabled by default) to prevent surprise costs, and that early access (Frontier program) participants have a grace period until July 1, 2026 before usage costs begin. This discussion prepared attendees for the practical and financial considerations of deploying advanced AI services in their organizations.
Microsoft Scout and “Autopilot” Agents: The event also briefly mentioned “Microsoft Scout,” another new AI initiative unveiled at Build 2026, as part of looking at future trends. Scout is an always-on, autonomous AI “autopilot” agent that proactively assists users across Teams, Outlook, SharePoint, and more. Given the workshop’s focus was shaped by attendees and many were more interested in immediate productivity topics over speculative AI features, the discussion around Scout and similar advanced AI agents was kept high-level, with an emphasis on monitoring these developments. Attendees were encouraged to stay informed about how these technologies (like Scout and Copilot enhancements) could eventually be leveraged to increase productivity once they mature and align with business needs.
Other Microsoft 365 Updates: The trainer and participants also reviewed a roundup of recent updates across the Microsoft 365 ecosystem. This likely included improvements from the 2026 roadmap and Microsoft Build announcements, such as:
- SharePoint & Teams: UI changes and new integrations (e.g., enhancements in Teams performance and architecture from the new “Teams 2.0” client).
- Windows & Endpoint: Possibly relevant news like Windows Autopatch or Intune updates for devices were noted if attendees raised them (especially given interest in Autopilot and device management in other events).
- Other: Additional Q&A on miscellaneous topics arose organically, reflecting the open format. For instance, participants asked about *license management and cost optimization (prompted by the Copilot discussion), and data backup/restore scenarios in M365 (how to recover deleted items or sites). The instructor addressed these with best-practice advice and references (sometimes with follow-up resource links provided).

Session-by-Session Highlights (Daily Schedule)

While the content was organized flexibly around attendees’ interests, the day’s four sessions can be summarized as follows:

Key Takeaways & Actionable Insights from TechWerks 30

The TechWerks 30 workshop delivered a rich collection of practical lessons for attendees. Each participant left with concrete knowledge and improvements to implement in their environments, underscoring the value of these deep-dive sessions. Some of the top key takeaways and actions were:

Adopt “Add to OneDrive” for Shared Content: Rather than syncing entire document libraries, leverage OneDrive shortcuts to access shared folders/libraries. This approach saves local storage space, reduces sync errors, and simplifies user workflows. Participants were encouraged to audit their current SharePoint/OneDrive usage and train users on using**“Add shortcut to OneDrive”** for easier file access and collaboration.
Optimize OneDrive Storage: Ensure your organization’s OneDrive for Business quotas are properly configured to avoid storage shortages. Increase default storage to 5 TB per user (for eligible Microsoft 365 plans) via the Admin Center or PowerShell (using Set-SPOTenant OneDriveStorageQuota commands). This proactive step is crucial for growing businesses.
Implement Conditional Access Baselines Safely: Put in place a strong set of baseline security policies (e.g., require MFA, block legacy auth, restrict risky locations) to protect user accounts. Use available tools (such as Microsoft’s built-in templates or community best-practice scripts) to quickly deploy these policies. However, always configure prerequisites (like named locations for trusted IP ranges or geographies) before enabling location-based blocks, to avoid inadvertently locking out admins or users.
Leverage Automated Tenant Posture Assessments: Utilize scripts or tools that scan your Microsoft 365 tenant’s security posture to highlight areas needing improvement. One script demonstrated at TechWerks 30 provided a comprehensive “health check” of the tenant’s configurations, revealing misconfigurations and improvement opportunities (to the surprise of attendees). Regular posture assessments help ensure you keep up with best practices and address any gaps.
Prepare for AI Integration: Keep an eye on new Microsoft 365 AI features like Copilot Cowork and Microsoft Scout that are on the horizon. Although many small businesses may not deploy these immediately, understanding their capabilities (e.g. Copilot’s usage-based billing and requirement for Azure subscription for cost control) helps in future-proofing your strategy. Plan ahead by considering how agentic AI tools could deliver value to your organization when you’re ready, and ensure your environment (licensing, governance, training) can support them.

Why Attend TechWerks Deep-Dive Sessions?

TechWerks events are not ordinary training days – they are a unique blend of community-driven agenda and practical immersion in Microsoft cloud technology. Key reasons why these sessions offer exceptional value include:

Attendee-Led Content: You shape the day. Participants vote on the agenda beforehand, ensuring the workshop covers topics you want to learn about, rather than a generic preset syllabus. This targeted focus means each session is highly relevant to the challenges and interests of those in the room.
Hands-On, Not “Death by PowerPoint”: TechWerks sessions are workshop-style, emphasizing live demos, real-time problem solving, and interactive labs over slide presentations. Every concept is illustrated in the context of actual real-world Microsoft 365 scenarios, making learning more engaging and practical. One attendee praised this*“interactive nature of the day” as “so much better than death by PowerPoint”*.
Small Group, Big Impact: Capped at 20 attendees, these sessions provide an intimate setting for one-on-one interaction with the expert instructor and peers. Everyone’s questions get answered, and the peer discussions help participants learn from each other’s experiences. The face-to-face environment fosters networking and deeper engagement, adding value beyond what online training can offer.
Immediate Best-Practice Takeaways: Each TechWerks event yields a wealth of actionable insights and best practices that attendees can implement right away in their businesses. As Mike H., a past participant, noted:“It is such a good format… the whole interactive nature of the day [is] so much better than death by PowerPoint.” Attendees leave with knowledge and tools that produce immediate improvements – from quick wins (like optimizing OneDrive usage) to strategic guidance (like strengthening your M365 security posture).

In summary, TechWerks 30 not only covered a variety of technical topics tailored to the audience’s needs, but also demonstrated the power of an open, hands-on format that transforms training into collaborative problem-solving. By emphasizing active learning, real-world practice, and participant-driven content, the session showcased why TechWerks’ full-day deep dives are invaluable for IT professionals seeking to stay ahead in the fast-moving world of Microsoft 365 and cloud services. Participants gained knowledge, confidence, and concrete best practices – making a strong case for the ROI of attending such face-to-face deep dive sessions.