Get PnP PowerShell to connect to my Sharepoint online tenant

Question

I get the following error "Connect-PnPOnline : The Login server cannot issue the requested compact encrypted ticket because a Data Encryption Key (DEK) has not been uploaded to the site." when I try to connect my Sharepoint Online tenant with PnP PowerShell. Any ideas how to solve this problem?

Answer 1

I did some trouble shooting and resolved the error that was being generated on sign in.
The error was: "error-->

"Connect-PnPOnline : AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '00000003-0000-0ff1-ce00-000000000000'."

I created another account for PnPPowershell usage with different authentication and it is working now.

Answer 2

Hi @nader hadjebi ,

Users might get that error if they are not global admin. Please check your account roles.
Microsoft 365 admin center > Users > Active users > click user name > Roles

And have you check you PowerShell codes? you could try the following PnP PowerShell codes to check wether you still get this error.
PnP PowerShell codes:

$SiteURL="https://tenant-admin.sharepoint.com/"  
$UserName="your user name"  
$Password = "your password"  
   
$SecurePassword = ConvertTo-SecureString -String $Password -AsPlainText -Force  
$Cred = New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $UserName, $SecurePassword  
   
#Connect to PNP Online  
Connect-PnPOnline -Url $SiteURL -Credentials $Cred  

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

I just had success connecting using a different powershell
Connect-SPOService -url https://mysiteurl-admin.sharepoint.com
I will be working on my follow on tasks tomorrow and will only then know if I run across any issues. So far so good. If there will be a need for a follow up post I will post one, but this new powershell script appears to have answered my question.