See more about SharePoint Conference 2019 here.
Office 365 Groups retention policies are very helpful to reduce orphaned groups in an organization’s tenant. Kindly, the Office 365 system sends out notifications to inform the group owner(s) to renew a group – or that a group will be deleted. What, if you oversee such a notification? See here how to restore an Office 365 group – thanks soft delete!
When working with Office 365 and Exchange services, it can be helpful to work with groups instead of users, for example, for allowing a group to have full access to a shared mailbox. In this case, there are some things to consider. See the working result in this documentation.
RBAC was introduced in Exchange 2010 to allow precise permission management within the Exchange organization for administrators and users. With RBAC, you can configure and control in a very granular way the administrative tasks that administrators or users can perform. RBAC controls both the administrative tasks that can be performed and the extent to which users can now administer their own mailbox and distribution groups. Understand that, with RBAC, it doesn’t matter what Active Directory permissions you have when using Exchange management tools—everything is authorized and controlled via RBAC. You can define precisely which cmdlets and parameters a user can run or modify.
1st MVP Award for Dominik Hoefling in Office Servers and Services.
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.
In part one, we saw how the Microsoft Graph API enables programmatic access to Office 365 groups. Now it’s time to let Azure Functions help us with the desired workflow.
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!
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.
Office 365 users often ask about user profiles in various Office 365 services and where to change what. Since the Office 365 products do have a history, there are different places where user profile data is stored and how specific properties are synchronized. So, we at atwork thought that it makes sense to inform about the current user profile status in Office 365 with this article.
Office 365 Groups provide a bunch of useful features for collaboration. In some cases, users want to send emails from an Office 365 group as sender. Here’s the HowTo” to accomplish SendAs” permissions to an Office 365 group for users.
Als Experte in allen Bereichen rund um Microsoft-Technologien und Cloud-Themen ist unser Mandant ein gesuchter Berater bei seinen Kunden. Sie werden Teil eines eigenständigen und verantwortungsbewussten Teams, in dem ein hohes Qualifizierungsniveau, immer auf aktuellstem Stand, höchste Priorität hat.
I recently had a curious behavior in my customers Exchange 2010 SP3 hybrid environment with centralized mail transport for Exchange 2010 SP3 Edge servers enabled. Before I describe the topic in more detail I would like to say thank you to the guys from Microsoft: Timothy Heeney, Scott Landry and Tom Kern helped me with my 'little' mail flow problem . Appreciate your help. My customer is using a smtp gateway for external mail flow as usual. Some of the mailboxes have configured smtp forwarding like ForwardingAddress (mail contact) and ForwardingSMTPAddress (external smtp address directly set on the mailbox). As we all know, Exchange hybrid mailbox move will not migrate the ForwardingAddress configuration for mailboxes. For this and some other migration limitations my colleague Andreas from atwork developed an 'Exchange Online Migration Tool' which is used by my customer. This tool checks, amongst other things, if the forwarding recipient is synced to Azure Active Directory and will set the smtp forwarding again after migration, let's say it's one component of many hybrid pre and post-migration tasks. However, not all smtp domains which are used for smtp forwarding are created in the on-premises environment nor in Exchange Online. Also, some of these smtp domains don't have any mx records populated in external DNS configuration. Mail flow for these domains is handled by the internal smtp gateway with some special configuration and different connectors. After the pilot migration of some Exchange 2010 users to Exchange Online, I saw a couple of '450 DNS socket error' messages during mail flow checks. As I said not every smtp domain has its own MX record published. The first thing I checked was the CMC connector which looked like this: RecipientDomains * SmartHosts [x.x.x.x],[x.x.x.x] TlsDomain contoso.com TlsSettings DomainValidation IsTransportRuleScoped False RouteAllMessagesViaOnPremises True It seems that everything looks good. Next, I was looking for the X-MS-Exchange-Organization-AuthAs mail header which had the value 'Internal' and centralized mail transport is used. All mail flow tests from different Exchange Online tenants and external mail provider were routed through the on-premises environment correctly - except for those who have smtp forwarding configured. This behavior for users with smtp forwarding configured is by design and EOP will route these emails directly to the Internet. Tom provided me the official support link: https://support.microsoft.com/en-us/help/3194415/some-messages-aren-t-routed-through-the-on-premises-organization-when-you-use-centralized-mail-transport 'This behavior is by design. To forward the message, an exact copy of the original message is created and sent to the external recipient. Mail routing logic sees that this new message originated in the on-premises environment and therefore doesn't send the message back to the on-premises environment. Instead, it's routed directly to the external recipient domain through Exchange Online Protection.' Nevertheless, if you are in the same situation, you can use the following tasks to get centralized mail transport working: Configure your domains properly and create it as an internal relay domain for both on-premises and Exchange Online Don't migrate these recipients to Exchange Online, set the domain to internal relay and let do your on-premises environment the resolving Rewrite it to something which is routable if you don't want to use centralized mail transport for the on-premises organization Remove the external smtp forwarding