Microsoft 365 services depend on identity
Exchange Online, SharePoint, OneDrive, Teams, licensing, and administration all rely on identity, authentication, permissions, groups, and roles. This hub connects those layers so troubleshooting starts with the dependency that can prove the problem—not just the service showing the symptom.
Begin with the reviewed material that is available now, then use the category map to see where future Microsoft 365 learning will fit.
Reviewed tutorial · SharePoint and OneDrive
Establish the source of truth, compare web and local copies, and separate identity, relationship, restriction, permission, and migration evidence before changing client state.
Open the sync investigation guideReviewed tutorial · Microsoft Entra ID
Select the correct event and correlate authentication, policy, device, network, client, application, and resource evidence without changing the tenant.
Open the Entra investigation guideReviewed tutorial · Exchange Online
Follow an evidence-based procedure for an archive mailbox that is not reducing primary mailbox usage.
Open the archive tutorialReviewed tutorial · Permissions
Verify shared-mailbox permissions, allow for propagation, and test the client path before rebuilding anything.
Open the shared-mailbox tutorialLearning method
Understand the environment, investigate useful evidence, make deliberate changes, and verify the original failure.
Review the learning pathEach lane has one primary home here. Published links appear where reviewed material exists; the remaining cards define the practical scope without claiming a release.
Published material available
Mailbox permissions, Outlook behavior, archive processing, retention holds, and the evidence needed to separate configuration from processing.
Browse Microsoft 365 tutorialsPublished investigation guide
Begin with sign-in and Conditional Access evidence. Broader tenant identity, user, and synchronization guidance remains in development.
Investigate Entra sign-insContent in development
Authentication methods, sign-in context, policy evaluation, exclusions, and safe ways to distinguish access policy from application behavior.
Published material available
Service permissions, group-backed access, administrative roles, propagation, and verification—currently represented by shared-mailbox troubleshooting.
Read permission case KT-000001Published synchronization investigation guide
Begin with evidence-first synchronization investigation. Broader sites, sharing, permissions, versioning, migration, and administration guidance remains in development.
Investigate synchronizationContent in development
Teams, groups, meetings, membership, file dependencies, and the service boundaries that make collaboration issues cross-platform.
Content in development
License assignment, service plans, activation state, entitlement checks, and how to verify whether access exists before troubleshooting the client.
Tutorials provide the repeatable procedure. Cases preserve the investigation, competing explanations, and judgment behind it.
Exchange Online · Archive
Check archive state, policy and tag assignment, retention-hold state, processing, and mailbox statistics in sequence.
Use the procedureExchange Online · Outlook
Verify permissions and propagation before testing automapping, restarting Outlook, or adding the mailbox manually.
Use the procedureMicrosoft Entra ID · Published investigation
Match the correct event and separate authentication, Conditional Access, device, network, client, application, and resource observations from conclusions.
Use the investigation guideSharePoint and OneDrive · Published investigation
Map the account, sync root, relationship type, item state, permissions, restrictions, and migration context without resetting or unlinking OneDrive.
Use the sync investigation guideContent in development
Future reviewed guides will expand authentication, Conditional Access, broader SharePoint and OneDrive administration, Teams, licensing, and identity-dependent troubleshooting.
The public library currently contains a Windows DNS tool. Microsoft 365-specific downloads are not published yet.
Microsoft 365 PowerShell
Future reviewed tools will emphasize read-only discovery, attributable output, narrow parameters, and safe verification for Microsoft 365 administration.
Current library
The library explains KrippyTech's read-only-first tool design and clearly separates the public Test-KTDNS release from private future baselines.
Visit the PowerShell LibraryCurrent downloads
The Downloads page currently contains Test-KTDNS v1.0.0 for Windows DNS troubleshooting; it does not claim a Microsoft 365 release.
View the current download catalogThe published cases use synthetic or anonymized details while preserving the troubleshooting logic, evidence chain, and verification.
KT-000001 · Exchange Online / Outlook
See how permissions, propagation, automapping, and client behavior were separated during the investigation.
Read KT-000001KT-000002 · Exchange Online / MRM
Follow the evidence that distinguished valid configuration from a stale retention hold and incomplete processing.
Read KT-000002Future case lanes
Identity, authentication, collaboration, licensing, and additional service cases will be linked here only after review and sanitization.