See more about SharePoint Conference 2019 here.
Recently I got an error in my PowerApp when trying to get an Office 365 User Profile, although this was working before: The service returned an error: Office365Users!MyProfile: {"status":402,"message":Insufficient privileges to complete the operation.","source":"127.0.0.1"}”. See here how to deal with such scenarios!
Mit dem Motto Wir digitalisieren Österreich #DigitaleHelden” startet Microsoft eine Digitalisierungs-Kampagne mit Gewinnspiel. Wir von atwork freuen uns, mit dabei zu sein und informieren über die neuesten Microsoft Cloud Technologien und zeigen eine PowerApp für den täglichen Gebrauch im Unternehmen. Schauen Sie rein und machen Sie mit!
Delegate365 version 6.2 comes with some updates and improvements. See the new features described here.
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
Your computer is still bound to your company’s local domain? How old school. Well, here’s a step-by-step guide how to join Azure Active Directory (AAD Join) with Windows 10!
In Office 365, it’s possible to define that just specific users are able to create Office 365 groups. if you set such a policy, does this also affect the creation of Microsoft teams? Well, see the answer here!
We enjoyed being part of aOSDay Dublin on March 15th, 2017, organized by the aOS Community. See some snapshots here.
Office 365 Groups spannen sich über mehrere Office 365 Services und stellen gemeinsame Arbeitsbereiche für Teammitglieder dar. Ende Februar hat AvePoint ein Webinar mit den Experten Ragnar Heil (Microsoft), Robert Mulsow (AvePoint) und Martina Grom (atwork) produziert. Hier gehts zum Webinar Office 365 Groups: Sie fragen, unsere Experten antworten”.
The cloud train started some years ago. Today, it’s no longer the question IF you will use the cloud, but WHEN you will use the cloud”. That’s the direction IT is going. See my top five reasons why your organization and your IT can benefit from using cloud services.
Since the beginning, Delegate365 developed to an extensive cloud solution for Microsoft Office 365. This article delivers a short overview about the components of Delegate365 in the Microsoft Cloud.
At the end of last year, Delegate365 version 6 was announced. We added a bunch of features and before updating all tenants, we wanted to improve some functionality. So it took some time to develop and test new features. Now it’s time to update all existing Delegate365 tenants to the latest version 6.1. See the most relevant news at a glance here!
This week, we have been at Microsoft Tech Summit Johannesburg, South Africa. The event took place in Sandton Convention Center from 6th to 7th February 2017 and hosted over 50 technical sessions with a range of topics as Microsoft Azure, hybrid platforms, DevOps, app platform, productivity, collaboration and more. Read more here!