Azure Function and SharePoint PnP PowerShell are mixing up the client context
Hi, I'm experimenting with Azure Function, Logic apps/Flow to replace an existing SharePoint Workflow. I've found a weird issue where the client context get mixed up when multiple flows are running in parallel and try to call the azure function. I've found a workaround to overcome this issue by allowing only one job on the azure function environment. It's not a good solution, therefor I want to find the root cause of the following error message : Exception calling "Load" with "1" argument(s): "The object is used in the context different from the one associated with the object." Has someone encounter a similar issue? Cheers Bernd
Turn on O365 alerting when Admin role is activated?
Hi all 🙂 I am wondering how I turn on alerts when a role is activated through O365 rather than Azure AD. I have PIM setup for Azure AD, but when an Admin role is assigned/activated through the O365 portal, then I do not receive an alert. Any and all help is appreciated 🙂
How to enable "Azure AD B2C Security group" for use in SharePoint that in the the Parent Azure.
I have created an Azure B2C Tenant under the existing subscription ( Azure AD that has P1 License ). Now I want to create a Security Group in the B2C Tenant. How do I make this group appear on SharePoint to share or add ?Re-hosting (Lift and shift )SharePoint 2016 on Premise Environment to Azure
we have an existing SharePoint 2016 on-premise environment having HA as backend SQL server 2016 always on failover cluster. two web servers, two application servers, and 1 office web app server. All servers are virtuals. The requirement is to rehost the complete environment in azure. I mean they want to complete lift and shift the environment from on-premise to Azure. The first question is possible? if yes what is recommended way to do that The plan is to use a standard azure migration tool to copying the VMs. I want to understand, is there are any guidelines to do the same. Need to know if there will be any impact on SharePoint Farm. I heard that it is complex to reshoot the SQL server 2016 always-on cluster in azure. There is the possibility to use Microsoft SQL Managed service. In that case, the instance name of the hosted database will change (as per my understanding). In that case, changing the instance detail from cliconfig.exe from all SharePoint server, will it help. Please advice.
