blog.atwork.at

news and infos about microsoft, technology, cloud and more

Provisioning an Office 365 group with an approval flow and Azure functions-part 3

This article describes the workflow for the group provisioning process by using the Azure function from part two in combination with PowerApps, SharePoint Online and Flow to enable a good user experience. Technically, we already have the toolset with the ProvisionGroup function. Now let’s create the rest.

Provisioning an Office 365 group with an approval flow and Azure functions-part 1

Office 365 groups span over various Office 365 services and provide a great way for collaborating. By default, every user can create an Office 365 group. While self-service is a good thing and many businesses adopted into that direction, some companies still prefer the controlled approach. In real world environments, organizations usually want to restrict the group provisioning so that IT can control the wild growth of groups. This article series shows how to create an Office 365 group with an attached approval process with SharePoint Online, Flow and Azure functions. See how this works here!

Delegate365 and the Exchange issue update

In the last days, some customers of Delegate365 experienced a warning in the Delegate365 portal that informed about the failing communication to Exchange Online. This issue was caused by the Microsoft Exchange Online PowerShell endpoint. We are glad to announce that this issue should be fixed soon.

Use Azure AD app principal without user context

For an application registered in AAD to be able to run in application context only without a user context the Company Administrator” role has to be assigned to the application in order to be able to access administrator endpoints for APIs like the Microsoft Graph. No additional permissions have to be assigned to the application after assigning this role.The assignment has to be done using PowerShell and looks like this: (the app registration has to be done beforehand)Install-Module AzureADConnect-AzureAD$app = Get-AzureADServicePrincipal -SearchString "your app name"$role = Get-AzureADDirectoryRole | Where-Object { $_.DisplayName -eq "Company Administrator" }Add-AzureADDirectoryRoleMember -ObjectId $role.ObjectId -RefObjectId $app.ObjectIdNote that you have to replace the string your app name” with the name provided to your app registration. The script intalls (if not already installed) the AzureAD PowerShell module and uses the contained commandlets to get the service principal of the app registration by name, gets the Azure AD Directory Role Company Administrator” and adds this role to the service principal of the app. After the role has been added, the app might, e.g., make queries to the user endpoint of the Microsoft Graph API to get properties from any users in the AAD.

Why we moved away from Exchange distribution groups to Office 365 groups

A very simple use case let us give up our Distribution lists. This article discusses why and how we did it and delivers tips how to improve your experience with Office 365 groups.
How can you replace old” distribution groups from a synced environment with new” Office 365 groups? And how to add, delete or modify email addresses to an Office 365 group? This article shows the steps.

Working With Office 365 Groups And Connectors article series at MVP Award Blog

Recently, the Microsoft MVP Award Program Blog published my three-part series about Working With Office 365 Groups And Connectors”. Read the articles online in the MVP blog here.

Gain access as delegated partner to another Office365 tenant with PowerShell

The goal was administer an Office365 tenant as delegated partner. But, currently I had difficulties to access another Office365 tenant in the Microsoft Partner Portal. When selecting a partner and opening the Office 365 admin center, not the partner tenant was opened but instead my own tenant. I didn’t figure out why this no longer was working. Anyway, I tried to use PowerShell instead…