Sebastain Gomes

Learners need to see how these pieces connect before any single feature makes sense. The advanced Conditional Access post follows the same logic in reverse: labelled Part 2, it assumes viewers already know the fundamentals.

The beginner overview uses one everyday analogy: an office security guard who knows who you are, where you are going, what you can access and whether you should be allowed in today.

Read original · Original 2

Authentication Context is introduced as a way to trigger step-up authentication only when someone accesses sensitive data or performs a high-risk action, rather than at every login.

• The SSO post opens with the frustration of remembering multiple passwords.
• Both walk through configuration and finish by testing the result, making the test part of the tutorial rather than an afterthought.

The Authentication Context video covers what the feature is, how c1, c2 and similar values are used, how it works with Conditional Access, real-world use cases, and how to configure and test it in Entra ID. The SSO post lists four concrete outcomes, ending with a test of the complete sign-in experience.

Read original · Original 2

The Conditional Access series is pitched as practical, advanced and real-world, and tagged for an exam-adjacent, identity-security audience.

The post for "Conditional Access | Advanced Techniques – Part 2" promises four techniques for strengthening Entra ID security and implementing Zero Trust, and tags SC-300, IAM and Identity Protection. The post text does not name the techniques; ask for the linked video to review them.

Read original

The stated goal is to share knowledge, help people learn and contribute to the technology community. Audience comments, subscriptions and feedback motivate them to keep producing.

A milestone post celebrates passing 17,000 views, calling it more than a number because each view represents someone who took a few minutes to learn something new. It also lists the topics coming next: Microsoft Azure, Microsoft Entra, Microsoft 365, cloud, security and emerging technologies.

Read original

The post announces Part 2 of an advanced Conditional Access series, describing four techniques to strengthen Microsoft Entra ID security and implement Zero Trust.

• It tags SC-300, IAM, and Identity Protection, signaling an exam-adjacent, identity-security audience.
• Ask for the linked video to confirm which four techniques it covers.

For brands planning a campaign

For a training company planning advanced Conditional Access material, this shows how Sebastain Gomes packages advanced topics in numbered, multi-part video series with certification and Zero Trust keywords. The format could inform a proposed series; review the video for its specific techniques.

The video connects separate capabilities into a single platform story.

Uses a plain-language analogy: an office security guard knows who you are, where you are going, what you are allowed to access, and whether you should be allowed in today.

• It then lists the components of Microsoft Entra ID: identity, MFA, Conditional Access, SSO, PIM, Access Packages, Identity Governance, B2B, and security.
• The video is explicitly positioned as a beginner-friendly overview.

For brands planning a campaign

A natural opening episode for an Entra ID series. The security-guard analogy and component map offer a reusable way to introduce identity governance and Conditional Access to newcomers before moving to deeper topics.

It starts with a common pain point and spells out what the video covers.

Opens with the problem, “Still asking users to remember multiple passwords?” and promises a step-by-step demonstration of configuring Single Sign-On for an application in Microsoft Entra ID.

• Learning outcomes include configuring an Enterprise Application, setting up SAML-based SSO, configuring SSO parameters, and testing the complete sign-in experience.
• The named audience includes Entra ID administrators, Azure professionals, IAM engineers, and cloud security learners.

For brands planning a campaign

Demonstrates a task-completion format with a clear before-and-after problem statement. For an SSO episode, it offers a model for scoping, naming outcomes, and addressing a specific technical audience.

Useful for readers who know Conditional Access basics and want practical advanced configuration.

Explains Authentication Context as a way to trigger step-up authentication only when someone accesses sensitive data or performs a high-risk action.

• The video covers six points: what Authentication Context is, how c1, c2, and similar values are used, how it works with Conditional Access, step-up authentication and stronger MFA, real-world use cases, and how to configure and test it in Entra ID.
• The post URL slug references PIM security, while the post body covers Authentication Context; confirm the intended label before citing it under PIM.

For brands planning a campaign

A fit for an advanced identity governance or Conditional Access series. The c1 and c2 detail and step-up authentication framing point to material for experienced administrators rather than beginners; pair it with the Conditional Access episode for a coherent advanced track.

They use a simple analogy: an office security guard who knows who you are, where you are going, what you can access, and whether you should be allowed in today.

Explainer video built around one platform map and an everyday analogy.

For brands planning a campaign

Useful for an introductory episode that orients viewers before advanced Conditional Access material. Identity Governance appears only in the platform list; for a governance-focused brief, ask for additional sourcing or a dedicated treatment.

Examples: Source 1

The post positions the material as practical, advanced, and real-world, with hashtags pointing to SC300 and IAM topics.

Advanced video series installment, positioned as a follow-up to earlier Conditional Access content.

For brands planning a campaign

Direct evidence for an advanced Conditional Access video series. The post does not list the four techniques; ask for a treatment or outline to see how the episode would cover them.

Examples: Source 1

They cover how c1, c2, and similar values are used, how the feature works with Conditional Access and stronger MFA, real-world use cases, and how to configure and test it.

Concept-to-configuration tutorial, moving from security purpose to setup and testing.

For brands planning a campaign

Strong fit for advanced identity security content, especially around Zero Trust, Conditional Access, and phishing-resistant MFA. Review the video itself before final campaign approval; the post describes it but does not reproduce the full transcript.

Examples: Source 1

It covers configuring an enterprise application, setting up SAML-based SSO, configuring SSO parameters, and testing the full sign-in experience. The post addresses Entra ID administrators, Azure professionals, IAM engineers, and cloud security learners.

Practical implementation walkthrough for administrators and identity engineers.

For brands planning a campaign

Suitable for implementation-focused training and sponsor placements around identity, SSO, or application access tools. This is a configuration demo, not an identity governance treatment.

Examples: Source 1

Gomes describes the channel's goal as sharing knowledge, helping people learn, and contributing to the technology community, with upcoming topics across Microsoft Azure, Microsoft Entra, Microsoft 365, Cloud, Security, and emerging technologies.

Channel milestone and community update.

For brands planning a campaign

Shows a video-first training format with an existing learner audience and a stated topic range. For a sponsorship decision, request subscriber count, watch-time data, and engagement metrics.

Examples: Source 1

They show subject matter and platform focus, not a sponsorship, partnership, or employment relationship. No commercial tie to Microsoft is disclosed.

View example

The relationship between Xanthe Tech and the creator is unstated.

View example

One post describes an identity model built from standardized attributes and dynamic groups that drive licensing, policy and access control in Entra ID and Intune, with Conditional Access policies rolled out in report-only mode first. Another explains how one person runs IT for 150 users with no MSP, addressing the same administrator audience Gomes teaches.

McMillan narrates a real build—what was migrated, deployed and documented, and why—while Gomes teaches viewers to apply a feature or setting in their own tenant. Conditional Access appears in both, but McMillan treats it as part of an operating model; Gomes presents it in a numbered series installment on advanced techniques.

Read original · Original 2

The coverage also explains how Conditional Access and privileged access fit into a wider authentication review, overlapping directly with Gomes’ phishing-resistant MFA and Conditional Access material.

Dowden writes for CIOs and technology leaders, framing the change as a strategy and roadmap decision with dated milestones and a five-step list of actions.

• Elsewhere, Dowden argues about MSP cost and vendor alignment.
• Gomes writes for administrators who will configure and test the setting, showing how it works rather than making the executive case for it.

Read original · Original 2

Both treat hybrid work and cloud adoption as drivers of identity and device decisions.

Bisagno addresses business and governance audiences, keeping security at the level of policy, risk and phased adoption, without product-level configuration. Gomes assumes a technical reader and explains how to set up and test a named Entra ID feature.

Read original · Original 2

The posts show a full migration from reseller-managed Microsoft 365 licensing to a direct provider model; a custom identity model driven by attributes such as account type, company, department, location and role tier; Conditional Access deployed in report-only mode first; and documented standards for group structure, device categories, rollout gates and change control.

• A second post shows the same operator explaining how one person runs IT for 150 users without a managed service provider, using centralized intake, identity as the control plane and automation as the default.
• It reports roughly four times the ticket volume, about 90% faster first response and about 60% shorter time to resolution.
• For a buyer whose series must show that a design holds up under real operating pressure, this is stronger evidence than product-by-product tutorials.

The tradeoff is that this is a narrative of one organization’s deployment, not a repeatable curriculum.

• Its posts offer no ordered lesson path, per-feature configuration walkthrough or video series with running times, so a training company would need to build the course structure.
• They also cover fewer individual Entra ID concepts, such as Authentication Context or SAML single sign-on, than Sebastain Gomes’s episodes.
• Ask for a lesson outline and configuration examples before committing.

Examples: Source 1 · Source 2

The post on Microsoft retiring provider SMS and voice authentication in Entra ID gives exact dates—1 February 2027 for retirement and 1 September 2026 for automatic passkey enablement—and turns them into a five-step migration plan: understand exposure, migrate before September, handle user experience and communication, check recovery processes, and use the change to reduce wider identity risk.

• It offers decision guidance for senior buyers, including which parameters to review, which user groups carry the most risk and how authentication strategy connects to phishing resistance in an AI-enabled threat environment.
• It also provides recent, timely material for a buyer who wants Entra ID content without an administrator-level lab.

The tradeoff is that this is strategy and adoption guidance, not configuration instruction.

• The posts offer no hands-on demonstrations, portal steps or troubleshooting detail, so a series built from them would need someone else to supply the lab and how-to segments.
• Its focus is the executive decision rather than the practitioner task—the opposite emphasis from Sebastain Gomes’s tutorial episodes.
• Ask for a lab plan and configuration walkthroughs if the series needs practical instruction.

Examples: Source 1 · Source 2

The posts treat security as a governance initiative balancing productivity, compliance and employee experience; argue that every personal device accessing company resources adds risk; and point to Device Trust models as the direction organizations are moving.

• A second post frames cybersecurity as a business-resilience issue rather than an IT concern and describes a phased route into Zero Trust that avoids a large infrastructure transformation, with device posture validation alongside user identity.
• This suits a training company seeking an executive-facing companion piece to a technical series.

The tradeoff is distance from the administrator’s task.

• The posts are article-first and governance-level, with no Entra ID configuration, Conditional Access policy design or step-by-step lab, so they cannot carry the advanced portion of an Entra ID series.
• Use them for framing or as a second voice on device trust, and ask for a separate technical instructor to provide the hands-on teaching.

Examples: Source 1 · Source 2