Merge branch 'dev' into feature/import-flow

Author: gautamdsheth

CHANGELOG.md

@@ -15,6 +15,7 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).
 
 ### Changed
 - Improved `Get-PnPTerm` cmdlet to show a better error message. [#4933](https://github.com/pnp/powershell/pull/4933)
+- **PnP PowerShell is now requires PowerShell 7.4.0 or newer**
 
 ### Fixed
 - Fix `Set-PnPView -Aggregations` parameter not showing aggregations in SharePoint online. [#4868](https://github.com/pnp/powershell/pull/4868)

MIGRATE-2.0-to-3.0.md

@@ -1,6 +1,6 @@
 # Updating from PnP PowerShell 2.x to 3.x
 
-The 3.x version of PnP PowerShell is based exclusively on .NET 8.0, which means that it will not work on older PowerShell editions like PowerShell 5.1, ISE or PowerShell 7.3 or older. It will work only on **PowerShell 7.4.6 or later editions.**
+The 3.x version of PnP PowerShell is based exclusively on .NET 8.0, which means that it will not work on older PowerShell editions like PowerShell 5.1, ISE or PowerShell 7.3 or older. It will work only on **PowerShell 7.4.0 or later editions.**
 
 ## Steps to update from 2.x to 3.x
 
@@ -14,7 +14,7 @@ Or
 
 - For Mac OS environments, please use [this link](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-macos)
 
-Once PowerShell 7.4.6 or later is downloaded and installed in your environment, you can install the PnP PowerShell module like you normally do.
+Once PowerShell 7.4.0 or later is downloaded and installed in your environment, you can install the PnP PowerShell module like you normally do.
 
 ```powershell
 Install-Module -Name "PnP.PowerShell"
@@ -28,7 +28,7 @@ Install-Module -Name "PnP.PowerShell" -AllowPrerelease
 
 ## Changes needed in Azure DevOps/GitHub Actions/Pipelines
 
-If you are using PnP PowerShell in Azure Devops, GitHub Actions or other pipeline infrastructure, you will have to update your PowerShell version from v5 or v7.2.x to v7.4.6 or later.
+If you are using PnP PowerShell in Azure Devops, GitHub Actions or other pipeline infrastructure, you will have to update your PowerShell version from v5 or v7.2.x to v7.4.0 or later.
 
 Recommend reading these 2 links:
 

README.md

@@ -14,7 +14,7 @@ For more information about installing or upgrading to this module, please refer
 
 ## IMPORTANT - New PnP PowerShell 3.x
 
-We released a new major version of PnP PowerShell, version 3 and upwards. This version of PnP PowerShell requires as of today PowerShell 7.4.6 or newer, and is based upon .NET 8.0. 
+We released a new major version of PnP PowerShell, version 3 and upwards. This version of PnP PowerShell requires as of today PowerShell 7.4.0 or newer, and is based upon .NET 8.0. 
 
 We have created a [guide](https://github.com/pnp/powershell/blob/dev/MIGRATE-2.0-to-3.0.md) for upgrading from previous versions to PnP PowerShell 3.x. If you are still using PowerShell 5.1 or the ISE, and want to use the latest major or nightly release, you will need to specify the required version like below: 
 

build/Build-Debug.ps1

@@ -172,7 +172,7 @@ if ($LASTEXITCODE -eq 0) {
 	Author = 'Microsoft 365 Patterns and Practices'
 	CompanyName = 'Microsoft 365 Patterns and Practices'
 	CompatiblePSEditions = @('Core')
-	PowerShellVersion = '7.4.6'
+	PowerShellVersion = '7.4.0'
 	ProcessorArchitecture = 'None'
 	FunctionsToExport = '*'  
 	CmdletsToExport = @($cmdletsString)

build/Build-Nightly.ps1

@@ -163,7 +163,7 @@ if ($runPublish -eq $true) {
 	GUID = '0b0430ce-d799-4f3b-a565-f0dca1f31e17'
 	Author = 'Microsoft 365 Patterns and Practices'
 	CompanyName = 'Microsoft 365 Patterns and Practices'
-	PowerShellVersion = '7.4.6'	
+	PowerShellVersion = '7.4.0'	
 	ProcessorArchitecture = 'None'
 	FunctionsToExport = '*'  
 	CmdletsToExport = @($cmdletsString)

build/Build-Release.ps1

@@ -96,7 +96,7 @@ if ($LASTEXITCODE -eq 0) {
 	Author = 'Microsoft 365 Patterns and Practices'
 	CompanyName = 'Microsoft 365 Patterns and Practices'
 	CompatiblePSEditions = @('Core')
-	PowerShellVersion = '7.4.6'
+	PowerShellVersion = '7.4.0'
 	ProcessorArchitecture = 'None'
 	FunctionsToExport = '*'  
 	CmdletsToExport = @($cmdletsString)

dependencies.json

@@ -1,6 +1,6 @@
 {
-  "Updated": "20250529-030001",
-  "PnPPowerShell": "2a72db6c17ed1d810d4780b8a722fac0c8c56c8b",
-  "PnPFramework": "1766dd9958dc1e3a8a4aabd3f5f23460b171d136",
-  "PnPCore": "9833e136c85f197966cb98def3fc699b9214a8a8"
+  "Updated": "20250606-025945",
+  "PnPPowerShell": "9fa3fb78e8ac8fa568f671993481e9d92beaac4d",
+  "PnPFramework": "80625626d66bb4d16e74bb5a3a91eb707430f16f",
+  "PnPCore": "0d7e8a4c17034491f8d4c80f4621c62ea24b437c"
 }

pages/articles/acsdeprecation.md

@@ -10,7 +10,7 @@ Simple: replace them with a proper Entra ID Application Registration.
 
 If the `_layouts/apprenew.aspx` was done in December 2024 or later, it will already [have created an Entra ID Application registration](https://learn.microsoft.com/sharepoint/dev/sp-add-ins/add-ins-and-azure-acs-retirements-faq#when-i-use-appregnewaspx-the-created-acs-principals-show-up-in-entra) for you. To validate this, simply take the Client ID/App Id of your application, go to [Entra ID](https://entra.microsoft.com), navigate to Identity > Applications > App registrations, click on the "All applications" tab and search for your Client ID/App ID. If it yields a result, it means your application also exists in Entra ID. If you go into the Entra ID Application registration and click on API permissions you will likely see no permissions being added to it. This is a clear indicator that this application registration has been done through `_layouts/appregnew.aspx` in or after December 2024, that it created an Entra ID Application registration counterpart, but that it still leverages ACS for its authentication. Add the required permissions here to ensure you can use this Entra ID Application registraton going forward.
 
-If you cannot find an entry in Entra ID with the same Client ID/App ID, it means the `_layouts/appregnew.aspx` operation has been done before December 2024 and no entry exists for it yet in Entra ID. You can [manually create your own new Entra ID Application registration](registerapplication.md#manually-create-an-app-registration-for-interactive-login) or use [Register-PnPAzureADApp](Register-PnPAzureADApp.html#example-7) to create one for you.
+If you cannot find an entry in Entra ID with the same Client ID/App ID, it means the `_layouts/appregnew.aspx` operation has been done before December 2024 and no entry exists for it yet in Entra ID. You can [manually create your own new Entra ID Application registration](registerapplication.md#manually-create-an-app-registration-for-interactive-login) or use [Register-PnPAzureADApp](../cmdlets/Register-PnPAzureADApp.md#example-7) to create one for you.
 
 ## How to I find out about which ACS Application Registrations my tenant has
 
@@ -51,7 +51,7 @@ The above example again would map to:
 
 - Sites.Selected
 
-Use [Grant-PnPAzureADAppSitePermission](Grant-PnPAzureADAppSitePermission.md) to set FullControl permissions on it.
+Use [Grant-PnPAzureADAppSitePermission](../cmdlets/Grant-PnPAzureADAppSitePermission.md) to set FullControl permissions on it.
 
 ## What do I need to change in my code?
 

pages/articles/installation.md

@@ -1,6 +1,6 @@
 # Installing PnP PowerShell
 
-You need PowerShell 7.4.6 or later to use PnP PowerShell. It is available for Windows, Linux and Mac and can be [installed through here](https://learn.microsoft.com/powershell/scripting/install/installing-powershell).
+You need PowerShell 7.4.0 or later to use PnP PowerShell. It is available for Windows, Linux and Mac and can be [installed through here](https://learn.microsoft.com/powershell/scripting/install/installing-powershell).
 
 ## Stable build
 
@@ -34,7 +34,7 @@ docker run -it m365pnp/powershell
 
 # Updating PnP PowerShell
 
-If you already have PnP PowerShell installed and just want to update to the latest version you can follow these steps. If you're not sure if your version is already up to date, it does no harm to run it anyway. If there's no new version available, it will not do anything. You need PowerShell 7.4.6 or later to use PnP PowerShell. It is available for Windows, Linux and Mac and can be [installed through here](https://learn.microsoft.com/powershell/scripting/install/installing-powershell).
+If you already have PnP PowerShell installed and just want to update to the latest version you can follow these steps. If you're not sure if your version is already up to date, it does no harm to run it anyway. If there's no new version available, it will not do anything. You need PowerShell 7.4.0 or later to use PnP PowerShell. It is available for Windows, Linux and Mac and can be [installed through here](https://learn.microsoft.com/powershell/scripting/install/installing-powershell).
 
 ## Stable build