---

This section details on the original issue you should resolve

<issue_title>Add UUID v7 support to New-Guid</issue_title>
<issue_description>### Summary of the new feature / enhancement

Dotnet 9 got support for creating UUID v7 GUIDs.

• Dotnet method [guid]::CreateVersion7(): https://learn.microsoft.com/en-us/dotnet/api/system.guid.createversion7

This could be useful in PowerShell too.

• Relevant cmdlet: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/new-guid

Proposed technical implementation details (optional)

• Default to v4 like now, but add optional switch for UUID v7, and optional DateTimeOffset as input.
• New cmdlet New-Ulid?</issue_description>

<agent_instructions>The @PowerShell/wg-powershell-cmdlets discussed this, we believe that users of New-Guid are only looking for a GUID/UUID and don't care about the technical aspects of it. As such, we believe it's better to move to the newer v7 UUID for the cmdlet. Users who want to differentiate between v7 and v4 (previous) are already technical enough to call the [Guid]::CreateVersion7() or [Guid]::NewGuid() for themselves. The docs should be updated to reflect this change and examples using PowerShell to call .NET APIs for specific versions of GUIDs.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@iSazonov There are some great [discussions](https://github.com/dotnet/runtime/issues/103658) in .NET repository. It clearly states that users consider which UUID version with a higher number to be better than which version with a lower number, and they also do not understand which version has its own scope. So they decided not to enhance the Guid class, but to make a separate specific (low level) API for experts.

The Guid class implements version 4, which is strong crypto, and New-Guid follows this most secure approach. The use of other UUID versions should be in community modules designed for special scenarios.

@SteveL-MSFT It's not clear to me if there's a downside to simply having `New-Guid` generate v7 UUIDs @SteveL-MSFT The @PowerShell/wg-powershell-cmdlets discussed this, we believe that users of `New-Guid` are only looking for a GUID/UUID and don't care about the technical aspects of it. As such, we believe it's better to move to the newer v7 UUID for the cmdlet. Users who want to differentiate between v7 and v4 (previous) are already technical enough to call the `[Guid]::CreateVersion7()` or `[Guid]::NewGuid()` for themselves. The docs should be updated to reflect this change and examples using PowerShell to call .NET APIs for specific versions of GUIDs.