Azure AD SCIM Validator is in General Availability (GA) Status
You can now validate the compatibility of your SCIM provisioning endpoint and Azure AD code base using our Azure AD SCIM Validator. This tool can be used by ISVs who want to build SCIM compatible servers either for gallery app or generic app and developers building their line of business SCIM apps. https://learn.microsoft.com/azure/active-directory/app-provisioning/scim-validator-tutorialProvisioning Azure Database for MySQL - Single Server from AKS
To gain the benefits of using a MySQL database in a Kubernetes application, a common strategy is to provision the database in a container running in a pod. In doing so, the database will use the cluster resources. Accessing the database from other pods in the same AKS cluster running client apps is possible via Kubernetes networking. However, if for some reason cluster resources become unavailable, both the application and the database will be unavailable, as both rely on cluster health. To address this issue, you can substitute the local database in AKS with Azure Database for MySQL, which will separate the database from the AKS cluster.
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 BerndPNP Template Provisioning Document Sets
I am trying to create a PNP Provisioning template of a site and then apply this to other modern sites, but one of the content types on it is not playing ball. It's a document set and in the properties it has default content of 5 files to create 5 folders. I don't need the files but, at least through the GUI, you have to put dummy files in to create 5 folders automatically when the document set is created, which is the brief. When I create the provisioning XML, all the default files are stripped out of the document set content type. How do I go about doing this in PNP? I would settle for how to do this in PowerShell against an SPOSite, as I could run it after creation of the main sites from the templates.Cross-tenant synchronization unable to provisioning group
Hello, I'm trying to sync some groups from a tenant to another, but the log return this error: Result Skipped Description Group '31d81b35-5725-40f5-9242-02a100363959' will be skipped. EntityTypeNotSupported SkipReason EntityTypeNotSupported ReportableIdentifier 31d81b35-5725-40f5-9242-02a100363959 This issue occurs with any kind of group, m365 or security. Users seems works. What could I do to address this issue?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?
Team provisioning issues - Owners not seeing Team
We’re using the Teams PS Module version 1.0.1 to provision Teams. A script creates a Unified Group using a Global Tenant account, then adds a user as a member to the UG, then promotes the user to an Owner, and again adds another Member and promotes them to Owner, finally a Team is created off this UG and the Global Tenant account is removed. From a process perspective this is working most of the time, however we’ve found that since fall 2019, occasionally, one or both Owners are not able to see the Team in the client or web. From the tenant, everything seems to be provisioned correctly, however the only way to resolve the issue is by removing the Owner (demoting to Member, deleting from Team and adding back). We had a ticket open with MSFT, however they are reporting it’s a timing issue and we need longer delays in the process to ensure that the ownership changes are completing in time. However if this was the case, I wouldn’t expect to see the correct owners in management. Also, I would expect that after a few hours, the Owner would eventually see the Team. This is not the case, even after 2 weeks in some cases. Is anyone else experiencing this issue or have a workaround?
