GTconsult

06/10/2026

"Just move the latest version" sounds simple until someone asks which one's latest. Every organisation has a file 214 versions deep, and at least one of them is called ACTUAL_FINAL_use_this_one_2. Migration doesn't create that mess. It just makes someone finally decide what's worth keeping.

Full breakdown- Version History and Migration: What Actually Gets Moved (And What Doesn't): https://www.gtconsult.com/blogs/post/version-history-and-migration-what-actually-gets-moved-and-what-does-not

29/09/2026

"Weekend job" and "40,000 items with broken permissions" don't belong in the same sentence, but they always end up there. Migration timelines aren't wrong because people are bad at estimating. They're wrong because nobody scoped the permissions mess first.

Full breakdown- Why Your SharePoint Migration Timeline Is Wrong (And How to Fix It): https://www.gtconsult.com/blogs/post/why-your-sharepoint-migration-timeline-is-wrong-and-how-to-fix-it

23/09/2026

Last July, Tumi got pickpocketed.

The phone was replaceable. What wasn't was everything still connected to it: email, Teams, company data. Because it was Intune enrolled, our team could wipe it remotely and close every door before anyone walked through.

The whole story comes down to how much access we hand to a phone without thinking about it. That includes how we prove who we are. For a lot of businesses, the sign-in code still arrives by SMS. Whoever has the phone, or the number, has the code.

Microsoft has reached the same conclusion. SMS and voice MFA in Entra ID retire on 1 February 2027, and passkeys take their place. A passkey is tied to your device and your fingerprint or face, so a stolen phone or a hijacked number isn't enough to get in.

The change is happening either way. What's still up to you is whether your team is ready for it, or finds out at a blocked sign-in screen.

What's changing and how to prepare 👇
https://www.gtconsult.com/blogs/post/entra-id-is-retiring-sms-and-voice-mfa

16/09/2026

Spoofing attacks don't work because they look dangerous. They work because they look exactly like something you already trust.

It's a game of looking beyond the typos at this point.

Read our full breakdown on spoofing attacks here: https://www.gtconsult.com/blogs/post/the-psychology-behind-sharepoint-spoofing-attacks

09/09/2026

The riskiest assumption in a SharePoint migration isn't the technical one. It's believing it'll be simpler than it actually is.

It's got a name, the planning fallacy, and it's why smart, experienced teams still consistently underestimate cost, time, and risk on a migration project, even when they've been burned by the exact same thing before.

Learn why this keeps happening, and how to deal with it: https://www.gtconsult.com/blogs/post/the-riskiest-assumption-in-a-sharepoint-migration

07/09/2026

Watching someone else demo a solution is easy. Building your own version, with your own data, is where the real work starts.

Most AI pilots don't fail because the model doesn't work. They fail in the space between an impressive demo and a system that has to run on real data, inside real systems, every day.

We've actually built one of these ourselves, not a demo, a real agent, on our own CRM data, for our own sales team.

Read our full piece on why most AI pilots stall before production: https://www.gtconsult.com/blogs/post/why-ai-pilots-fail-the-demo-always-works-production-doesn-t

19/08/2026

Text message codes for MFA are being retired.

Microsoft is pulling SMS and voice authentication out of Entra ID from 1 February 2027. Passkeys are now the default.

Here's why it matters. SMS and voice are some of the easiest MFA methods to phish, SIM-swap, or replay. Passkeys close all three.

Auto-enrolment starts 1 September 2026. If you haven't moved your users off SMS or voice by then, Microsoft starts moving them for you.

What's changing, the key dates, and how to get ahead of it before the deadline:

Microsoft is retiring SMS and voice MFA in Entra ID on 1 February 2027. Here's what's changing, the key dates, and how to move your business to passkeys before the deadline.

06/08/2026

Think you might be exposed to a SharePoint vulnerability? Here's the two-minute check: log onto your SharePoint servers and check your Windows updates for the KB reference tied to your latest security patch. Then cross-reference that KB against Microsoft's Security Update Guide by searching the relevant CVE number directly. That guide shows you exactly which version you're on and whether the fix has already been applied.

Heads up: Microsoft has a new SharePoint patch landing on 12 August addressing a serious on-premises vulnerability. If you're running SharePoint on-prem (Subscription Edition, 2019, or 2016), watch for that release and get it installed as soon as it's out. SharePoint Online / M365 is not affected. Patches are released monthly, so always check against the current KB rather than a number you saw last month.

28/07/2026

A breach isn't the scary part. What happens after is.

When attackers steal IIS machine keys, they're not just getting in, they're planting malware inside the same trusted system that serves content to every one of your users. Your SharePoint environment becomes the delivery mechanism, sending malicious links to people who have no reason to question them because the request is coming from somewhere they already trust.

"It's now this trusted place where code can live that gets served to your users." — Kyle Farr, GTconsult Security Analyst

Watch the full breakdown of the SharePoint CVEs and what to check today: https://www.youtube.com/watch?v=_iFFg7Zjya4&t=2s