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.

This is not just a technical detail. Nebula.KB-dev is a clone of Nebula.KB built to follow the development versions of the various modules, so it usually reflects what will later appear in production releases before the public site does.

In practice, if a Nebula module is about to get new features, fixes, or important changes, the updated documentation is very likely already available on Nebula.KB-dev first.

That does not mean kb.gioxx.org is "old" or should be ignored. It simply serves a different purpose: the main site remains the stable reference for the released version, while the -dev branch is the right place to see what is coming next.

In short:

• kb.gioxx.org = documentation for the production version
• Nebula.KB-dev = documentation for the development version
• if you want to see what is coming next, start with Nebula.KB-dev

When a Nebula module is being prepared for a new release, the -dev documentation is usually the best place to check first, even if some features are still being tested and may change before the official release.

Introduction​

Microsoft is retiring the -Credential parameter used when connecting to Exchange Online PowerShell. Starting with module versions released in July 2026 and later, the -Credential parameter will be removed from both Connect-ExchangeOnline and Connect-IppsSession cmdlets. Organizations using this parameter in automation scripts must migrate to a supported authentication method before that date. This change improves security by moving away from legacy authentication methods that do not support modern protections such as multifactor authentication (MFA).

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).

Here I will publish quick updates about:

• changes and improvements across the Nebula module family (or scripts);
• technical updates that affect scripts and automation workflows;
• Microsoft 365 announcements that can directly impact module development.

The goal is simple: keep a clear history of decisions, changes, and recommended actions so development, maintenance, and daily usage stay aligned.