What is Microsoft Data Amp?
A live virtual event on Thursday, April 19th about Microsoft’s latest innovations in data, analytics and artificial intelligence, with keynotes by EVP Scott Guthrie and CVP Joseph Sirosh. The event will include exciting announcements that will help you derive even more value from the cloud, enable transformative application development, and ensure you can capitalize on intelligence from any data, any size, anywhere, across Linux and other open source technologies.
Being a Microsoft MVP, I’m thrilled to announce that I’m going to host a Microsoft Data Amp Listening Party on 19-April in Lahore for all data experts to come and join us. In this party we will be talking and sharing the knowledge around data solutions of Microsoft and how I being an MVP started to learn the journey of Data Amp and what it has done in my experience for this.
To register for this local event in Lahore, please drop us an email with the following information at firstname.lastname@example.org
- Email Address
- Area of Expertise
- Your recent interaction with Microsoft Solutions
We’ve limited seats available.
Today on March 7th, 2017, Microsoft has announced the Microsoft Teams Global Availability. Per Microsoft announced, Microsoft Teams global availability celebration will start on Tuesday, March 14th at 8:30am PDT. The celebration agenda is going to be the Microsoft Teams Global Availability.
Microsoft will host an online event to celebrate Microsoft teams global availability and Microsoft Corporate Vice President Kirk Koenigsbauer and a special guest will share perspectives around new stuff in Microsoft Teams and how customers are leveraging Microsoft Teams in Office 365 to collaborate and be more productive.
You can register for online event by from here
Email spoofing is the most common challenge that every organization is facing in current digital world regardless of the size of the organization. Office 365 email protection with DKIM and DMARC helps organization to protect against spoofing that tend to have increased number of spam emails. DomainKeys Identified Mail (DKIM) and Domain-based Messaging and Reporting Compliance (DMARC) checks trusted authenticated sender to prevent untrusted senders from sending spoofed emails.
Inbound validation of DKIM and DMARC is supported in Office 365
What is DKIM?
Domainkeys Identified Mail (DKIM) is a method to validate a digitally signed messaged that appears in the DKIM Signature header in the message headers. It ties an email message to the organization responsible for the message.
More details on DKIM can be found on TechNet.
What is DMARC?
Domain-based Messaging and Reporting Compliance (DMARC) is designed to protect email spoofing when the phisher has spoofed the 5322.From email address that is the email address displayed in email clients like outlook. Sender Policy Framework (SPF) protect the phisher to spoof the emails from 5321.MailFrom. DMARC catches the case that is more deceptive. DMARC results are stamped in authentication header of email.
DMARC evaluate both DKIM and SPF and ensure that the domain matches the domain in 5322.From address. SPF does not protect against 5322.From spoofed emails.
Q: Helo woodgrovebank.com
Q: Mail from: email@example.com <– 5321.MailFrom
Q: Rcpt to: firstname.lastname@example.org
Q: To: “Andrew Stobes” <email@example.com>
Q: From: “Woodgrove Bank Security” firstname.lastname@example.org <– 5322.From
Q: Reply-To: “Woodgrove Bank Security” <email@example.com>
Q: Subject: Woodgrove Bank – Action required
Q: Greetings User,
Q: We need to verify your banking details. Please click the following link to accomplish this.
Q: Thank you,
Q: Woodgrove Bank
The end user will see this information as below.
This email can pass SPF check if the phisher has published the SPF check for woodgrovebank.com but as we know the phisher has spoofed the email using 5321.MailFrom and DMARC will fail on this email. DMARC configurations are already in place in Office 365 for inbound emails and you don’t have to configure anything. In next blog article, we will look into how we can configure DMARC for outbound emails in Office 365.
For more information on office 365 email protection with DKIM and DMARC, please go through the following posts.
When you are working with your customers to transition them to Office 365. One of the most important ask is to have customized Office 365 OWA URL to ease end users and have them not to remember something that is not related or company branded like outlook.office.com. I received these type of requests almost on all of my engagements when customers are moving to Office 365 from on-premises messaging environment to Office 365 or a 3rd party messaging system.
This blog post is not applicable when you have Exchange hybrid deployment. Exchange hybrid deployment has a lot of different things and scenario’s.
Office 365 OWA can be accessed by users by visiting the known URL of Office 365 i.e. http://portal.office.com and click on the Outlook icon to access the mails in Office 365. Users can also access their emails on OWA by visiting http://outlook.office.com URL but for users to have it customized Office 365 OWA URL to visit for accessing the emails is something that can be company branded like mail.msexperttalk.com?
In order to setup the OWA URL redirection for your organization’s customized Office 365 OWA URL, you need to create a CNAME entry in your public DNS to point to outlook.office.com.
Create CNAME record with the name of Mail and point it to outlook.office.com
Once the CNAME records are in place for both public and private DNS of the company, your users now can access OWA by using customized Office 365 OWA URL by visiting http://mail.domain.com and in my case it’s http://mail.msexperttalk.com. You can visit the Office blog site to see the details of other DNS records requirements for Office 365.
Recently, working with an enterprise customer, we came across an issue where Office 365 room mailbox permissions were not being applied correctly. Most of the time after we assign permission to a Room Mailbox in Office 365 the permissions were not synchronized correctly to outlook clients. We worked with Microsoft support for this issue but it seems to be a product “bug” but i cannot confirm this or it seems like PowerShell is the way to trust when working with workloads in Office 365. Troubleshooting Office 365 room mailbox permissions issue requires me to perform all level of testing and troubleshooting to ensure everything is in place but it wasn’t working properly. During the troubleshooting, we reassigned the permissions to a user on room mailbox via exchange online powershell and appropriately that seems to be working without any issue.
Troubleshooting Office 365 Room Mailbox Permission Issue
Working with Office 365, when you assign a user permission to room mailbox so that the user can add the mailbox to outlook client and can create appointments, During the process of adding a room mailbox to outlook client, we were prompted with the following error message.
The workaround for this issue that worked for us in our scanerio was to remove the permissions and reassign the permissions using powershell. To assign the permissions using powershell, perform the following steps.
- Retrieve the permissions being assigned to room mailbox using powershell
C:\> Get-MailboxFolderPermission -Identity firstname.lastname@example.org:\Calendar
- As you can see that i do not have the permissions to Calendar folder. Run the following cmdlet to assign permissions on calendar folder
C:\> Add-MailboxFolderPermission -Identity email@example.com:\Calendar -User firstname.lastname@example.org -AccessRights Owner
Re-run the Get-MailboxFolderPermission cmdlet to verify the permissions are being assigned to the user.
Once it’s done, restart outlook client and the permissions will start synchronizing and the user will be able to create/edit/delete calendar appointments to the conference room mailbox. The issue that i had faced could be due to some back end issues with Exchange online and I do not recommend that this could be the issue with all deployments but i have seen much more success with PowerShell as compared to GUI and i always recommend to leverage Powershell over GUI.