Below are the prerequisites to run this script as all the above requirements for the report can not be fulfilled just by using Teams module, we need to extract some stuff from the office 365 group object or you can say Exchange unified group.
Our SharePoint Support team got the request to Change the Title of the particular Site.(Modern Team Site)
When going to Site Settings they were not getting the option to Change the Title which they get with other Sites.
On other SharePoint online sites they see as below:(Classic Team Sites, Publishing Sites etc)
Reason is obvious, Modern Team sites that user creates are integrated to Office 365 group (we can call them as office 365 group site as well). In order to change the Name of office 365 group sites, you need to rename the office 365 group.
These sites are office 365 groups driven, uses Groups#0 template, all these kind of changes should be made on the group object rather that SharePoint Site itself.
Other such example is updating the owner of such site, that should also be done on Office 365 group object.
Go to Portal.office.com –> Admin –>Groups –> Search for office 365 group
Click on it & Edit Name
To Update the owner of the Office 365 group site, follow the same process, instead of Name, hit edit on Owners.
Now wait for few hours, Modern team Site title will get renamed and Owners will also get updated. (It can take upto 1 hr or more for changes to take effect)
Note: Url wil not change when renaming the Site Name, which is same behavior as any other sites on SharePoint.
My assumption in this post is that you are already aware about SharePoint List and how to add a Microsoft flow When item is created or modified.
Select the action after you have already triggered your flow, Search for the term Approval.
Select the Start an Approval Action.
You have two options here, either everyone must approve before it is counted as approved or First one to respond as approved.
Next action is to use Switch Case and capture the response of Approve and Reject action.
Here is how you will receive the approval email. (only thing with this approval activity which is different from Email with options flow is that it can not be sent from your organizational email address)
As an approver , when I will hit approve or reject, I will get option to submit with comments.
Another big benefit is you can even use your mobile device and have Flow App to perform these operations, it even sends you push notifications.
You can build your flow further and add other actions after Approval/Reject Switch Case that you have seen above,
For example adding a send mail action after approval and adding the comments from the approver on it.
You can use this technique to add Approval flow with comments in your Flow with one caveat that email will always arrive from Maccount@microsoft.com but there are other benefits like you can approve the request from the Flow Portal and also from Flow mobile App.
When Microsoft published that they will be retiring the office 365 Discovery Service API, We have logged a ticket with their support team and were able to get the Application ids that are not compliant with it.
We will be retiring the Office Discovery Service API from Office 365 as of November 1, 2019. You are receiving this message because our reports indicate that your organization uses one or more Office 365 applications that utilize the Office Discovery Service API.
Now next thing was to find the application names which was not much of a challenge and we were able to find it by searching the Application ID under portal.azure.com –> Azure Active Directory –> Enterprise Applications.
Now we know the applications but we want to export the user list that is involved which we were not able to accomplish thru the GUI.
Here are the steps that needs to be followed for exporting the user list of the Application.
Connect to AzureAd via PowerShell.
2. From the GUI you have already got the object Id of the Application.