On my first attempt I tied using the File Content variable directly within the body of the email, only to see binary… Note: This works fine when attaching the file as an ‘attachment’ (see Attachments Content).
Plus I struggled to find a way to convert binary to base64. That was before I realised I didn’t need to do all that work, hence this blog post…
This causes the Dependency and NuGet folders to show a warning triangle, however the project builds and the PnP ProvisioningTemplate loads OK.
I also attempted a downgrade of the Business Layer project SharePointPnPCoreOnline NuGet reference to version: 2.24.1803 (this references Newtonesoft.Json version 9.0.1), however the following code failed to work:
Working with the Content Type Hub and publish (syndicate) content types to other site collections; have you received an Access Denied message when selecting the “Refresh all published content types on next update”?
Well it turns out that you are denied access because the DenyAddAndCustomizePages is set to TRUE for that site collection.
To grant access to the “Refresh all published content types on next update” functionality you need to set the “Deny Add and Customize Pages” fag to false. This can be done simply, by running the following PowerShell:
Anonymous users are users who have a shareable link to a folder or document and can view or edit the document or upload to the folder (depending on the type of link) without having to log in with a username or password. Anonymous links can be freely passed around between users and are valid until you disable them or they expire (if you’ve set an expiration date).
Anonymous users cannot access sites, and you cannot assign them licenses. They can only view or edit the specific document or folder for which they have an anonymous access link.