I have encountered this error message a few times first hand, and I want to share what I did to work around it.
I have a Windows 2016 Server running the PDM and then I have my own workstation not connected to a domain.
In fact, when I reinstall Windows 10 it always convince me to use my Office365 credentials ending up logging me in as Windows Azure account.
This account is not present on the server and the user can't be added there as a member of a group (at least to my knowledge).
So, here is the trick I'd like to share with you.
On your workstation where the error is displayed, simply create a new LOCAL account.
The 'simply' is not as simple as it sounds because Microsoft hides this feature more and more deep in the account settings.
Currently running W10 Version 1803, these are the steps to create the local account:
Press Windows+i to open Windows Settings
Then select Accounts
Select 'Other People' and 'Add someone else to this PC'
The Microsoft account window opens and here you select 'I don't have this person's sign-in information'
Microsoft still try to convince you to use a Windows Account, but select the 'Add a user without a Microsoft Account'
The rest is straight forward, so not documented here.
Now switch windows user, but mind you, you most likely have to type in the login like this
Where LocalUser is the user you just created.
Now, when adding the vault views or adding the server to the Administration it all works.
Create the views with the local account and then simply logg off and log back in with your Azure account - the views are there and you have access to the PDM Administration.
If someone knows how to add the Azure account to the local group on the PDM Archive server please let me know here and this workaround becomes 'obsolete'