Best practice for provisioning Content Types on Modern Sites
Hi, I'm looking for the best way to work with content types on modern sites. Currently the Content Type Hub (cth) is used for our classic sites and can't be deactivated. We started a new project to provision modern sites wit PnP Provisioning Engine. If a modern site is created, the content types from the content type hub are not available for some time. Adding content types from the cth to list or libraries makes this impossible for the provisioning engine. I see a few options 1. Create a modern site that won't get the content types from the cth and add create content types manual on the template site collection. I don't see how we can technically make this possible... 2. Reuse the provisioned content types from the content type hub in the template site This might give a conflict when the content types are provisioned by the PnP Prov Engine and not by the content type hub, not sure if this is a valid argument. 3. Create (next to the one from the cth) new content types in the template site. there will be an overlap of content types... This approach makes it more difficult for reporting or search queries. I'm looking forward to your ideas or best practices. Cheers Bernd
Cannot provision SP modern site with Group programmatically - "Alias is already in use"
Hi, I'm building a solution that can provision O365 Groups with associated Modern Team Site and Teams. While trying to create some new Sites with Groups, sometimes the creation fails with the error message "The alias for the group already exists". Provisioning : Tried both using New-PnPSite from PnP PowerShell v2.28.1807.0 , as calling directly the REST API /_api/GroupSiteManager/CreateGroupEx with the same result (error) Payload: {"displayName":"TestPosh2", "alias":"13015", "isPublic":false, "optionalParams":{"Description":"","CreationOptions":{"results":[],"Classification":""}}} Response: {"error":{"code":"-2147024713, Microsoft.SharePoint.SPException","message":{"lang":"nl-NL","value":"De alias voor de groep bestaat al."}}} There isn't any visible existing Alias created in the tenant with that ID. To verify this I did check - Exchange Admin Center - Get-UnifiedGroup (Exchange) - Get-PnPUnifiedGroup - /_api/GroupSiteManager/GetValidSiteUrlFromAlias?alias='13015' They all return no matching data, the last one returns an OK status code with the available URL for site: http://tenant.sharepoint.com/sites/13015 How can I further see whether this alias can be in use, or successfully use it for the new site?