One documentation site, two versions per module
Nebula.KB-dev is gone. The documentation for the development versions of the Nebula modules now lives here, on kb.gioxx.org, next to the documentation for the released versions.
Nebula.KB-dev is gone. The documentation for the development versions of the Nebula modules now lives here, on kb.gioxx.org, next to the documentation for the released versions.
If you run a Nebula command with -GridView on PowerShell 7.6.6 and the console stops responding, the command is not slow and nothing is wrong with your tenant. On that release Out-GridView never returns and never opens its window, so the session is stuck until you close it.
Get-EntraGroupMembers "My Entra Group" -GridView # never returns on PowerShell 7.6.6
The bug is in PowerShell itself, not in Nebula: a plain Get-Process | Out-GridView freezes in exactly the same way. Every Nebula command that offers -GridView is affected until you either update Nebula.Core or avoid that PowerShell release.
Updating PowerShell and the Microsoft 365 administration modules should be a routine maintenance operation. Unfortunately, a currently open regression can make the latest Exchange Online and Microsoft Graph modules fail when they are used in the same PowerShell 7 session.
The failure was first confirmed with PowerShell 7.6.4, ExchangeOnlineManagement 3.10.1, and Microsoft.Graph 2.38.1. A follow-up test with Microsoft.Graph 2.39.0 still found a conflict in the same combined session: Graph connected after the order change, but Exchange Online WAM failed with a RuntimeBroker/NullReferenceException. In the original Nebula flow, the error appeared while Connect-Nebula was establishing the Microsoft Graph session:
Connect-MgGraph:
InteractiveBrowserCredential authentication failed:
Method not found: '!0
Microsoft.Identity.Client.BaseAbstractApplicationBuilder`1.WithLogging(
Microsoft.IdentityModel.Abstractions.IIdentityLogger, Boolean)'.
This is not a permissions, Conditional Access, consent, or token-cache error. It is an in-process assembly dependency conflict between Microsoft modules.
Nebula.KB-dev has been retired. The documentation for the development versions now lives on kb.gioxx.org as the Next version of each module. Read the announcement.
If you ever check both Nebula.KB-dev and kb.gioxx.org, there is one simple rule to keep in mind: the -dev documentation is usually the most up to date.
Based on customer feedback, Microsoft postponed the client-side removal of the -Credential parameter. New Exchange Online PowerShell module releases will stop supporting it beginning in December 2026, not July 2026 as originally announced.
The retirement has not been cancelled, but the additional time removes the immediate July deadline and gives administrators a longer migration window.
Microsoft is retiring the -Credential parameter used when connecting to Exchange Online PowerShell. Starting with module versions released in December 2026 and later, the parameter will be removed from both Connect-ExchangeOnline and Connect-IppsSession.
The change moves administrators and automation away from the Resource Owner Password Credentials (ROPC) flow, which cannot satisfy modern protections such as multifactor authentication and Conditional Access.
I have re-enabled the internal Docusaurus blog and, starting today, this space will be one of the reference points for Nebula project updates (the main one is and will remain my personal blog, but this is where English translations of those same articles can live, along with micro-updates that may have an impact on end users).