Search creators⌘K
  1. Home
  2. Creators
  3. Jeff Willinger

Jeff Willinger

Jeff Willinger works with organizations on Microsoft technology at Heartland Business Systems (HBS), focusing on Microsoft 365, Copilot and AI, security, Power Platform, and other Microsoft business tools. Their work includes helping businesses plan AI governance and adoption.

25.1K followersAI governanceCybersecurityDigital transformationBased on 10 posts · latest Sep 2026
LinkedIn

At a glance

They are most useful for practical Microsoft Copilot adoption, governance, security, and AI Center of Excellence guidance.

Best for

Fits Microsoft solutions integrators running enterprise Copilot governance and adoption campaigns.

Not for

Does not fit intranet, employee experience, HR, or internal communications culture campaigns.

Key takeaways

  • A 90-day Copilot Center of Excellence addressed inconsistent use and unclear ownership.
  • Reported outcomes: proposal time down 28%, executive prep down 35%, 14 workflows automated.
  • AI governance combines data governance, identity and access, risk and compliance, accountability.

Check first: Ask for LinkedIn follower analytics and recent engagement on Copilot governance posts.

Main ideas
AI governance is four jobs, not one · Copilot licenses are not the transformation; a Center of Excellence is · Security should start with business goals, and a risk assessment is only worth the decisions it triggers
Audience
25,146 LinkedIn followers
Read first
From Experiment to Enterprise: a 90-day AI Center of Excellence for Microsoft 365 Copilot
Ways to work together
AI Center of Excellence Implementation · Microsoft 365 Ecosystem Transformation · Enterprise Cybersecurity & AI Governance
Sources for this section

What they are known for

Jeff Willinger works in the Microsoft ecosystem at Heartland Business Systems, focusing on Microsoft 365, Copilot and AI, security, and related business tools.

  • Their posts connect technology plans to how organizations actually adopt and govern them.
  • In one case study, they describe a 90-day AI Center of Excellence for an enterprise that had deployed Copilot but lacked consistent use and clear ownership.
  • They also write about practical security priorities, including risk assessments that lead to decisions and protecting sensitive data in AI use.
  • Their career post describes more than 20 years across Microsoft technologies, consulting, partnerships, sales, and related work.

Willinger’s distinctive contribution in these examples is making Microsoft AI adoption concrete: they link governance, security, training, business ownership, and measurement rather than treating Copilot as a license rollout.

  • Their case study lays out specific steps, from permission cleanup and usage policies to role-based workshops and usage analytics, and reports results including reduced proposal and executive-preparation time.
  • Their security recap adds a useful counterweight: AI governance depends on data, identity and access, risk and compliance, and accountability working together.
  • Follow their work for practical Microsoft-focused perspectives on adoption and security; the three posts also include a personal career announcement, not just technical analysis.
Sources for this section

Ideas and priorities

Jeff Willinger’s writing returns to one argument: Microsoft 365 Copilot and AI produce value only when organizations govern them, and governance requires several jobs working together—not a policy written once.

Read more

The posts also outline a phased adoption model, a business-first view of security, and a specific claim about what data loss prevention must now cover.

AI governance is four jobs, not one

Willinger’s central claim is that AI governance is not a single artifact or compliance checkbox.

Read more

It comprises data governance, identity and access, risk and compliance, and accountability; skip any one, and the rest falls apart.

  • In practice, a single tool or policy will not fix an AI rollout.
  • The disciplines have to work together, starting with a clear view of the data, risks, and gaps.

In the Secure Iowa recap, Willinger says plainly that AI governance combines data governance, identity and access, risk and compliance, and accountability—and that skipping one brings the whole thing down. The Copilot case study puts that logic into practice: before scaling, the engagement cleaned up SharePoint and OneDrive permissions, refined Purview sensitivity labels, and ran a Copilot readiness assessment.

Read original · Original 2

Copilot licenses are not the transformation; a Center of Excellence is

Willinger says the common failure is deploying Copilot widely without anyone owning the strategy, leaving usage uneven and returns unmeasurable.

Read more

They recommend a phased Center of Excellence covering vision tied to business priorities, infrastructure readiness, policy and guardrails, role-based training, a business/IT cadence, and usage analytics. Their summary: deploying AI without a Center of Excellence is piloting, not transforming.

Willinger describes a $1.2B health and life sciences organization with more than 400 Microsoft 365 Copilot licenses, no governance model, and inconsistent usage.

  • IT owned the licenses, business leaders owned the expectations, and nobody owned the strategy.
  • The 90-day model they applied included five enterprise use cases tied to revenue and margin, an 'AI Champions' community in Teams, a prompt library in SharePoint, and a monthly cadence among the CIO, chief revenue officer, HR, compliance, and data leaders.
  • They report that within six months, proposal creation time fell 28%, executive prep time fell 35%, 14 internal workflows were automated, and Copilot expansion was approved.
  • These figures come from their account of the engagement.

Read original

Security should start with business goals, and a risk assessment is only worth the decisions it triggers

Willinger treats cybersecurity as table stakes and says reacting is not a strategy.

Read more

Their sequence is deliberate: understand business goals, analyze the threat landscape, find the gaps, prioritize, then execute.

  • A risk assessment that is prepared, shared, and filed without changing decisions has failed.
  • They also call third-party risk the biggest blind spot: vendor access, weak service-level agreements, and absent governance quietly create exposure.

Willinger’s Secure Iowa takeaways include a practical point: risk assessments matter only when their findings inform decisions, not when they sit in a report. The tools keep evolving—Defender, Purview, Entra, Sentinel, Intune, Copilot—but the fundamentals of knowing your data, risks, and gaps do not change.

Read original

Data loss prevention has a new job covering AI prompts and AI output

Willinger’s most specific technical position is that data loss prevention must keep sensitive information out of AI prompts and treat AI-generated output as governed data from the moment it is created.

Read more

That shifts DLP from an outbound data-exfiltration control to a safeguard within Copilot and generative-AI workflows.

Willinger highlights themes from a room of IT and security leaders grappling with expanding attack surfaces across cloud, hybrid work, and AI workloads, alongside ransomware, phishing, and identity attacks.

Read original

The effort is concentrated in the Microsoft partner channel and co-sell motion

Willinger’s priorities are Microsoft-shaped: Modern Work, Microsoft 365, Copilot, AI, Power Platform, Dynamics, and security, with an explicit focus on building co-sell opportunities with Microsoft.

Read more

They describe more than 20 years across SharePoint, intranets, digital transformation, sales, partnerships, consulting, and Microsoft MVP years as converging on this Microsoft-centered role.

In announcing the move to Heartland Business Systems, Willinger lists their areas of focus and says they will work on Microsoft and AI, solve business problems, and pursue co-sell with Microsoft. They also note roughly 25,000 LinkedIn followers, pointing to an audience largely made up of the partner and Microsoft-ecosystem community.

Read original

Sources for this section

Start with their work

From Experiment to Enterprise: a 90-day AI Center of Excellence for Microsoft 365 Copilot

Answers the question that stalls many AI governance conversations: what does a Copilot rollout look like once the licenses are live and value is uneven?

Read more

Willinger describes a project with a $1.2B health and life sciences company that had more than 400 Microsoft 365 Copilot licenses deployed but no governance model, inconsistent usage, and no clear owner of the strategy.

  • They lay out the 90-day phased Center of Excellence they implemented: vision and strategy tied to five enterprise use cases; infrastructure readiness, including SharePoint and OneDrive permission cleanup, Purview sensitivity labels, and a Copilot readiness assessment; policy and guardrails covering a usage policy and prompt governance; role-based workshops, a prompt library in SharePoint, and an 'AI Champions' community in Teams; a monthly business/IT cadence; and usage analytics.
  • They report results after six months: proposal creation time down 28%, executive prep time down 35%, 14 internal workflows automated, and approval to expand Copilot.
  • They close by arguing that deploying AI without a Center of Excellence is piloting, not transforming.
  • The performance figures are their account of the engagement; buyers should ask for the supporting measurement.

For brands planning a campaign

This is the most directly usable piece for a thought leadership webinar on AI governance and Copilot adoption.

  • The six phases map cleanly onto a session outline, and the reported metrics give an enterprise audience something concrete to discuss.
  • A Microsoft solutions integrator could ask Willinger to walk through the phases live and offer the prompt library and champion community as session takeaways.

Secure Iowa conference recap: risk assessment, third-party risk, and AI governance

Shows how Willinger frames security and AI adoption together, where governance decisions usually get made inside an enterprise.

Read more

Willinger recaps a conference where IT and security leaders discussed an expanding attack surface from cloud, hybrid work, and AI workloads.

  • Their takeaways are specific: a risk assessment matters only if its findings drive decisions rather than sit in a report; proactive security should start with business goals, then move through the threat landscape, gaps, prioritization, and execution, in that order; third-party and vendor risk remains the largest blind spot because of vendor access, weak SLAs, and absent governance; AI governance requires four things working together — data governance, identity and access, risk and compliance, and accountability — and falls apart if one is skipped.
  • They also argue that data loss prevention has a new job: keeping sensitive information out of AI prompts and treating AI output as governed data from the moment it is created.
  • They list Defender, Purview, Entra, Sentinel, Intune, and Copilot, while insisting the fundamentals of knowing your data, risk, and gaps do not change.

For brands planning a campaign

Offers a security-first entry point to the same Copilot governance conversation.

  • A webinar sponsor selling Microsoft security tooling can use this framing to position Copilot adoption as an extension of an existing risk program rather than a separate IT project.
  • The third-party risk point is a natural hook for partner and vendor audiences.

Joining Heartland Business Systems: what Willinger does now

Answers the basic placement question — where this person works, what they work on, and what their career looks like — so the rest of their work makes sense.

Read more

Willinger announces joining Heartland Business Systems, with a focus on the Microsoft ecosystem: Modern Work, Microsoft 365, Copilot, AI, Power Platform, Dynamics, security, and building co-sell opportunities with Microsoft.

  • They describe more than 20 years across the same territory — SharePoint, Microsoft 365, Dynamics, intranets, digital transformation, sales, partnerships, Power Platform, cybersecurity, and AI — including Microsoft MVP years, consulting years, and startup years.
  • They also write at length about the people and culture they encountered in the first weeks, and note roughly 25,000 LinkedIn followers.
  • The post is a personal career reflection rather than a technical argument.

For brands planning a campaign

Signals the audience Willinger reaches and their role in the channel: partner-side and Microsoft-ecosystem professionals, not just end-user IT buyers.

  • That makes them a better fit for partner-facing sessions on Microsoft co-sell and modern work than for a pure CIO-focused security panel.
  • A webinar on vendor-and-partner dynamics can draw on their channel perspective.
Sources for this section

Topics and approach

Posts cited for each topic
Practical, experience-based teaching style3
AI governance and Copilot adoption2
Business-first cybersecurity and risk assessment1
Microsoft ecosystem breadth and co-sell focus1

AI governance and Copilot adoption

Jeff Willinger writes about moving Microsoft 365 Copilot deployments from scattered experimentation to governed, measurable programs.

Read more

In a detailed case study, they describe a 90-day AI Center of Excellence for a $1.2B health and life sciences organization with 400+ Copilot licenses.

  • The program covers vision, infrastructure readiness, policies, training, business/IT alignment and usage analytics.
  • They argue that AI governance brings together data governance, identity and access, risk and compliance, and accountability.

Willinger outlines a phased, numbered AI Center of Excellence model with specific steps and Microsoft 365 alignment.

For brands planning a campaign

A thought leadership webinar on AI governance and Copilot adoption could use this framework and the reported outcomes—28% faster proposal creation, 35% reduced executive prep time and 14 automated workflows—to show enterprise clients a practical path from pilot to scale.

Examples: Source 1 · Source 2

Business-first cybersecurity and risk assessment

At the Secure Iowa Conference, Willinger argued that cybersecurity is table stakes and risk assessments matter only if they lead to decisions.

Read more

Their takeaways: start proactive security with business goals, treat third-party risk as a major blind spot, and use data loss prevention to keep sensitive data out of AI prompts and treat AI outputs as governed data.

For brands planning a campaign

Willinger can advise enterprise clients on connecting Microsoft security tools—Defender, Purview, Entra, Sentinel and Intune—to business priorities and practical risk reduction.

Examples: Source 1

Microsoft ecosystem breadth and co-sell focus

In a career announcement, Willinger describes more than 20 years across the Microsoft ecosystem: SharePoint, Microsoft 365, Dynamics, Power Platform, cybersecurity, AI, Copilot, intranets, digital transformation, sales and partnerships.

Read more

They say their role at Heartland Business Systems centers on Modern Work, Copilot, AI, Power Platform, Dynamics, security and creating co-sell opportunities with Microsoft.

For brands planning a campaign

A webinar could draw on Willinger’s broad partner perspective, particularly on co-sell motions and adoption across the Microsoft stack.

Examples: Source 1

Practical, experience-based teaching style

Willinger uses concrete examples, checklists and numbered frameworks, sharing lessons from direct work on a specific enterprise deployment and at a conference.

Read more

They frame their advice as reminders for better consulting. Their posts include a case study, a conference recap and a career announcement.

For brands planning a campaign

A webinar pairing a real deployment story with a governance checklist would suit Willinger’s approach and give attendees practical steps to take away.

Examples: Source 1 · Source 2 · Source 3

Sources for this section

Brands and businesses

The posts identify Jeff Willinger’s employment at Heartland Business Systems (HBS), where they work on Microsoft 365, Copilot and AI, security, Power Platform, and Microsoft co-sell.

Read more

They also describe Microsoft as the ecosystem at the center of their career and current work.

  • A third post describes a paid-style engagement with an unnamed West Coast health and life sciences enterprise.
  • The posts don’t mention sponsorship, affiliate, investment, or disclosed-partnership relationships.

Heartland Business Systems

Employment

They say they joined HBS and focus on Microsoft Modern Work, Microsoft 365, Copilot, AI, Power Platform, Dynamics, security, and Microsoft co-sell opportunities.

Read more

They also mention HBS when writing about the Secure Iowa Conference.

View example

Microsoft

Mention

They describe Microsoft as the center of their career, cite a period as a Microsoft MVP, and discuss client work involving Microsoft 365, Copilot, Purview, Defender, Entra, Sentinel, Intune, and Power Platform.

Read more

The posts don’t identify Microsoft as a sponsor or client; ask whether any commercial relationship exists.

View example

Sources for this section

Topics and similar creators

Jeff Willinger publishes on LinkedIn, so that feed is the place to start.

Read more

Begin with the detailed walkthrough of a Microsoft 365 Copilot AI Center of Excellence, which lays out a phased adoption model and the results they report from it, then read the Secure Iowa recap for the security and data-loss-prevention principles behind that model. The career post is the quickest map of the ground they have covered — more than 20 years across SharePoint, intranets, Microsoft 365, Power Platform, Dynamics, and security — and where their efforts now focus: Modern Work, Copilot, AI, and co-sell with Microsoft.

AI governance Microsoft 365 Copilot Microsoft 365 Cybersecurity Data loss prevention Microsoft Purview Risk assessment Digital transformation Power Platform Microsoft partner ecosystem Co-sell with Microsoft Case study Conference recap LinkedIn posts IT and security leaders Microsoft partner community

John O'Donnell

Writes from inside the Microsoft partner channel about alliances, channel motions, and the change programs that follow a Microsoft release, and how partners and enterprise customers turn product announcements into working deployments.

Read more

O'Donnell's posts centre on partner and alliance business development and on Dynamics 365 and agentic business applications, while Willinger focuses on Copilot governance, security, and the framework behind an AI rollout.

Read original · Original 2

E.C. Scherer-Malone

Both write short practitioner field notes about Microsoft data-security work and flag the same failure pattern: labels and policies built without a governing principle stop scaling.

Read more

Scherer-Malone stays within Purview, focusing on sensitivity labelling and DLP design mistakes, while Willinger treats data security as one of several elements in a broader Copilot and AI adoption program.

Read original · Original 2

Arvind Suthar

Both argue that Copilot cannot be switched on before the data layer is governed, and teach through concrete deployment lessons, checklists, and specific gotchas rather than general advice.

Read more

Suthar's material is a continuously updated reference for GCC High and CMMC-bound government contractors, with control mappings and regional constraints, while Willinger writes case studies and conference takeaways for a general enterprise audience.

Read original · Original 2

Sources for this section

Audience

Jeff Willinger's recorded LinkedIn audience is about 25,000 followers as of 8 October 2026.

Read more

Three posts suggest a professional audience interested in Microsoft 365, Copilot, Power Platform, and security: a detailed account of a 90-day Microsoft 365 Copilot Center of Excellence build inside a $1.2B health and life sciences organisation; governance takeaways from the Secure Iowa security conference; and a career announcement about joining Heartland Business Systems that names the Microsoft areas they work in.

  • That mix could suit a client case narrative better than a high-level keynote.
  • The posts don’t establish followers’ employers, job titles, seniority, or geography, and publish no engagement counts, impressions, or per-post reach.
  • Before committing, ask for LinkedIn follower analytics covering job function, seniority, and location, plus recent impressions and engagement on posts about Copilot governance or enterprise AI adoption, so you can compare the proposed webinar’s topic and format directly.

LinkedIn followers

25,146

LinkedIn profile record, observed 8 October 2026; not a per-post engagement measure · 2026-10-08

Sources for this section

Partnership options

Jeff Willinger is a specialized consultant and representative of Heartland Business Systems (HBS), guiding large enterprises through complex technology adoption and digital transformation.

Read more

Their expertise centers on the Microsoft ecosystem, particularly Microsoft 365, AI, Copilot and Power Platform.

  • Their engagements bridge technology implementation and measurable business value, often through structured governance frameworks such as an AI Center of Excellence to promote consistent, strategic use of enterprise tools.
  • Their work includes developing modern-work strategies, strengthening cybersecurity against evolving threats and identifying co-selling opportunities within the Microsoft community.

AI Center of Excellence Implementation

Buyer requirement

Requires a structured, phased approach, such as a 90-day model, to govern AI use, align Copilot with business priorities and reduce risk before large-scale deployment.

Microsoft 365 Ecosystem Transformation

Buyer requirement

Needs expert guidance across Microsoft technologies, including SharePoint, Dynamics, Teams and Power Platform, to modernize work processes and solve specific business problems.

Enterprise Cybersecurity & AI Governance

Buyer requirement

Requires proactive risk assessment and governance frameworks to manage the expanding attack surface created by cloud, hybrid work and AI workloads, while ensuring data safety and accountability.

Sources for this section

Campaign fit

A campaign to shortlist

Campaign need: a Microsoft solutions integrator wants a thought leadership webinar on AI governance and Copilot adoption for enterprise clients.

Read more

This is a strong fit for specific reasons, not just general reputation.

  • The most detailed example is a 90-day Microsoft 365 Copilot Center of Excellence built for a $1.2B health and life sciences company that already had 400+ Copilot licenses live, no governance model, and no clear owner of the strategy.
  • That is the kind of situation the proposed webinar would address, opening on a problem the audience recognises rather than on a product.
  • The post is organised into six numbered phases — vision and strategy, infrastructure readiness, policies and security, user enablement, business/IT alignment, and usage analytics — a structure that maps directly onto a webinar outline.
  • They also report outcomes a sponsor would want discussed publicly: proposal creation time down 28%, executive prep time down 35%, 14 internal workflows automated, and approval to expand Copilot after six months.
  • A second post, from the Secure Iowa security conference, offers a security-first entry point: risk assessments that lead to decisions, third-party risk as the biggest governance blind spot, and AI governance as data governance, identity and access, risk and compliance, and accountability working together.
  • A third post, announcing a move to Heartland Business Systems, establishes more than 20 years across SharePoint, Microsoft 365, Dynamics, Power Platform, Copilot, and security, plus a current focus on co-sell with Microsoft — useful for an integrator that relies on Microsoft co-sell motions.
  • The teaching format also suits the campaign: checklists, numbered frameworks, and direct lessons from engagements translate well to a live session and attendee takeaway.
  • Two points affect the sponsorship decision: the posts do not say whether the performance figures were independently audited, and the LinkedIn following shown here is about 25,000, with no breakdown by job function, seniority, or geography.

When to choose a specialist

Campaign need: an employee experience or intranet platform vendor wants a webinar for HR and internal communications leaders on workplace culture and modern intranets.

Read more

The topic is adjacent to their history — a career post lists intranets among more than 20 years of Microsoft ecosystem work — but the posts do not substantiate the audience or topic.

  • The intranet claim rests on a single word in a list within a career announcement; the posts show no intranet or employee experience project, client example, outcome, or argument about culture.
  • The two substantive posts are governance and security analysis for IT and security decision-makers: a Copilot Center of Excellence build and a conference recap on risk assessment, third-party vendor risk, and data loss prevention around AI prompts.
  • A vendor would be buying an inferred audience and topic, while HR and internal communications buyers would be evaluating a speaker whose work shown here is not addressed to them.
  • The LinkedIn following shown here is roughly 25,000, but there is no data on who those people are, so there is no basis for claiming reach into internal communications or HR roles.
  • For a culture-oriented campaign, there is another risk even if the topic were reframed: the posts contain no video, transcript, or slide content, so buyers cannot assess on-camera delivery.
  • The career post is a personal reflection, not evidence of an on-stage format.
  • If the vendor remains interested, the honest route is to change the campaign need rather than stretch the claims in the posts — for example, a session on how governed Copilot adoption changes the way work gets done and what governance must be in place before broader deployment, aimed at the IT and security audience the posts address.
A worked campaign example

Campaign angle for the enterprise AI governance campaign: 'From 400 Licenses to a Governance Model — a 90-Day Copilot AI Center of Excellence.' The integrator hosts; Willinger presents; the session runs 45 minutes with 15 minutes of Q&A, and the integrator's assessment offer is the next step, not the pitch.

Opening (5 minutes): frame the case study — 400+ Copilot licenses deployed, usage inconsistent, security cautious, legal nervous, executives asking for proof of value, IT owning the licences and business owning the expectations, with nobody owning the strategy. That framing makes the rest of the session feel like a real engagement rather than a capabilities talk.

Session body (30 minutes), following the existing sequence: vision and strategy, with five enterprise-level Copilot use cases tied to revenue and margin and an executive steering committee; infrastructure readiness, covering SharePoint and OneDrive permission cleanup, Purview sensitivity label refinement, and a Copilot readiness assessment before scale; policies and security, covering a usage policy, prompt governance guidelines, data classification, and monitoring through Defender and Purview; user enablement, covering a 30-minute executive briefing, role-based Copilot workshops, a prompt library hosted in SharePoint, and an AI Champions community in Teams; business and IT alignment, built on a monthly cadence between the CIO, chief revenue officer, HR, compliance, and data leaders; and usage analytics, covering Copilot usage frequency, prompt success rates, time saved on proposal development, and Power Platform workflows built. Close with the reported results — 28% faster proposal creation, 35% less executive preparation time, 14 workflows automated, expansion approved at six months — clearly identified as the client's own reported numbers.

Takeaway (one page, gated): a checklist based on the six-phase structure, with the decisions an enterprise must make at each phase and the readiness questions to answer before enabling Copilot more widely. The integrator's version of the checklist, with its assessment offer, follows as the thank-you page.

Promotion and measurement: LinkedIn organic from their account, where the following shown here is about 25,000, plus the integrator's own client list and any available Microsoft co-sell channels, given the co-sell focus in their current role. Track registrations, attendance rate, Q&A questions — governance versus licensing is a useful split — and the number of attendees who accept a follow-up readiness assessment.

Before committing spend, the integrator should settle four things.

  • Get permission to describe the client and repeat the 28%, 35%, and 14 figures publicly, or agree how to describe them if the client cannot be named.
  • Ask for LinkedIn follower analytics by job function, seniority, and geography, plus impressions and engagement on Copilot governance posts, to judge expected registration against the actual audience rather than a follower count.
  • Confirm whether any current employer or partner restrictions apply to a vendor-hosted webinar.
  • The posts publish no booking or inquiry path, so the initial approach would go through LinkedIn or the integrator's existing relationship.
Sources for this section

Who else to consider

John O'Donnell

For the same enterprise Copilot governance and adoption webinar, consider John O'Donnell if the integrator wants to emphasize Microsoft partnership strategy and the practical modernization of CRM and ERP estates.

Read more

A post about Dynamics 365 Activate frames AI as a way to assess existing customizations and usage before migration or modernization, which could support a session for organizations connecting Copilot plans to broader business-app changes.

The post is about Dynamics and partner ecosystems, not a Copilot governance programme or a measured adoption framework. Jeff Willinger's case study gives the webinar a more direct Copilot story: a six-phase Center of Excellence plan, security and enablement steps, and reported business outcomes.

Examples: Source 1

E.C. Scherer-Malone

Choose E.C.

Read more

Scherer-Malone if the webinar's main need is a focused, practitioner-level discussion of Microsoft Purview, sensitivity labels, and data protection foundations that affect Copilot readiness. The posts explain why labels organized by data type can become hard to use and scale, and why a proliferation of DLP policies may signal a problem with the programme rather than the technology.

These examples concentrate on Purview implementation and data security, rather than the wider adoption, business alignment, training, and outcome measurement in the Copilot Center of Excellence example.

Examples: Source 1 · Source 2

Arvind Suthar

Choose Arvind Suthar if the integrator needs the session anchored in GCC High, CMMC, or federal-contractor security decisions.

Read more

The posts describe a detailed Securing GCC High resource, including CMMC control mappings, security hygiene, assessment checks, and preparation of data before enabling Copilot in GCC High. That is a closer match for an audience facing those specific compliance and deployment constraints.

The posts are narrowly oriented to GCC High and compliance implementation; they do not show the broad enterprise Copilot adoption and governance programme in Jeff Willinger's case study. Their case study makes them the more directly evidenced choice for a general enterprise audience, while Suthar's work points to a specialized federal-cloud campaign.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Campaign brief: blank template

Example: enterprise Copilot governance webinar

Sources for this section

Research methodology

  • Jeff Willinger's LinkedIn posts here include a Microsoft 365 Copilot AI Center of Excellence case study, a recap of the Secure Iowa cybersecurity conference, and a post announcing a move to Heartland Business Systems.
  • These posts carry no publication dates, so no ordering or change over time is claimed.
  • No video, transcript, or slide material appears here.
  • The client engagement in the case study is described only in Willinger's own post; performance figures are as stated there and were not independently verified.
  • Willinger's posts do not say whether a particular book, show, or earlier project is a major reason people search the name; that question remains unresolved.

Brands they talk about