Update SPO AAD App / ACS App-Only articles with PnP Framework references (SharePoint#8794)

* Updating SharePoint Online AAD App / ACS App-Only granting process with PnP Framework, removing references to PnP Sites Core

* Updating code sample to latest console app template

Author: michaelmaillot

docs/solution-guidance/security-apponly-azureacs.md

@@ -1,7 +1,7 @@
 ---
 title: Granting access using SharePoint App-Only
 description: Granting access using SharePoint App-Only
-ms.date: 12/27/2022
+ms.date: 02/26/2022
 ms.prod: sharepoint
 author: vesajuvonen
 ms.author: vesaj
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 SharePoint App-Only is the older, but still very relevant, model of setting up app-principals. This model works for both SharePoint Online and SharePoint 2013/2016/2019 on-premises and is ideal to prepare your applications for migration from SharePoint on-premises to SharePoint Online. Below steps show how to setup an app principal with tenant full control permissions, but obviously you could also grant just read permissions using this approach.
 
 > [!IMPORTANT]
-> Azure Access Control (ACS), a service of Azure Active Directory (Azure AD), has been retired on November 7, 2018. This retirement does not impact the SharePoint Add-in model, which uses the `https://accounts.accesscontrol.windows.net` hostname (which is not impacted by this retirement). For more information, see [Impact of Azure Access Control retirement for SharePoint Add-ins](https://devblogs.microsoft.com/microsoft365dev/impact-of-azure-access-control-deprecation-for-sharepoint-add-ins/). For new tenants, apps using an ACS app-only access token is disabled by default. We recommend using the Azure AD app-only model which is modern and more secure. But you can change the behavior by running ‘set-spotenant -DisableCustomAppAuthentication $false' (needs the latest SharePoint admin PowerShell).
+> Azure Access Control (ACS), a service of Azure Active Directory (Azure AD), has been retired on November 7, 2018. This retirement does not impact the SharePoint Add-in model, which uses the `https://accounts.accesscontrol.windows.net` hostname (which is not impacted by this retirement). For more information, see [Impact of Azure Access Control retirement for SharePoint Add-ins](https://devblogs.microsoft.com/microsoft365dev/impact-of-azure-access-control-deprecation-for-sharepoint-add-ins/). For new tenants, apps using an ACS app-only access token is disabled by default. We recommend using the Azure AD app-only model which is modern and more secure. But you can change the behavior by running 'set-spotenant -DisableCustomAppAuthentication $false' (needs the latest SharePoint admin PowerShell).
 
 ## Setting up an app-only principal with tenant permissions
 
@@ -48,7 +48,7 @@ With the preparation work done let's continue to the next chapter showing how yo
 
 ## Using this principal with PnP PowerShell
 
-If you want to utilize the generated app-only registration with [PnP PowerShell](https://aka.ms/pnp-powershell), you can do so by connecting to your SharePoint On-Premises or Online environment using:
+If you want to utilize the generated app-only registration with [PnP PowerShell](https://aka.ms/pnp/powershell), you can do so by connecting to your SharePoint On-Premises or Online environment using:
 
 ```powershell
 Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/demo -ClientId [Your Client ID] -ClientSecret "[Your Client Secret]"
@@ -58,7 +58,7 @@ Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/demo -ClientId [Your
 
 ## Using this principal in your application using the PnP Framework library
 
-In a first step, you add the PnP Framework library nuget package: https://www.nuget.org/packages/PnP.Framework. Once that’s done you can use below code construct:
+In a first step, you add the PnP Framework library nuget package: https://www.nuget.org/packages/PnP.Framework. Once that's done you can use below code construct:
 
 ```csharp
 string siteUrl = "https://contoso.sharepoint.com/sites/demo";