Sensitivity labels are used to classify email messages, documents, sites, and more. When a label is applied (automatically or by the user), the content or site is protected based on the settings you choose. For example, you can create labels that encrypt files, add content marking, and control user access to specific sites.
Once we created the label policies we started to do some testing and noticed the following bounce message when we applied labels to emails:
Remote Server returned ‘550-5.7.162 OmeEncryptionAgent; Permanent Failure 550-5.7.162 Exception encountered: RmException. 550-5.7.162 Exception message: Failed to get template. Template:96be504d-7520-4645-8f23-06d0b61f9235. FailureCode:UnknownFailure. Recoverable:False.. 550 5.7.162 Please contact your system administrator for more information.’
After some research we identified that the labels had not been published as below:
The issue is caused by because the has not been a syncronisation between the Lables and Azure RMS. The following is a guide to forcing a syncronisation using PowerShell connecting to the AIP service:
1, Run the following command to install powershell module for the AIP Service:
Install-Module AIPService
2, Run the following command to enable the AIP service module:
Import-Module AIPService
3, Run the following command to connect to the AIP Service
Connect-AIPService
We then need to list all of the labels to see what the status is as below:
Get-AipServiceTemplate | FL name*, TemplateId , Status
All of the labels highlighted above as Archived have not yet sync’d to the Azure RMS service so the next command will force the label to sync, this will need to be done on each individual label as follows:
Set-AipServiceTemplateProperty -TemplateID "TemplateID" -Status Published
So an example below
Once you have ran the command you will notice that all label status’s will change to Published – we found that once the above process hads been completed the label can be applied and emailed successfully.
Microsoft have released the new Exchange Online PowerShell module today, This module supports modern authentication and includes faster alternatives to common cmdlets.
The Exchange Online PowerShell V2 module contains a small set of new cmdlets that are optimised for bulk data retrieval scenarios. Until you create a session to connect to your Exchange Online organisation, you’ll only see these new cmdlets in the module. After you connect to your Exchange Online organisation, you’ll see all of the older remote PowerShell cmdlets.
The EXO V2 module uses Modern authentication for all cmdlets. You can’t use Basic authentication in the EXO V2 module.
The new cmdlets in the EXO V2 module are meant to replace their older, less efficient equivalents. However, the original cmdlets are still available in the EXO V2 module for backwards compatibility after you create a session to connect to your Exchange Online organisation.
The new cmdlets in the EXO V2 module are listed in the following table:
Windows PowerShell needs to be configured to run scripts, and by default, it isn’t. To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window: Set-ExecutionPolicy RemoteSigned Notes:
You need to configure this setting only once on your computer. Read more about execution policies here.
If you don’t do this step, you’ll receive the following error when you try to connect:Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.
Close and re-open the elevated Windows PowerShell window to get the changes from the previous steps.
Run the following command from an elevated Windows PowerShell window: Install-Module -Name ExchangeOnlineManagement Enter Y to accept the license agreement.
Update the EXO V2 module
If the EXO V2 module is already installed on your computer, you can run the following commands to see the version that’s currently installed and update it to the latest version.
To see the version of the EXO V2 module that’s currently installed, run the following commands: Import-Module ExchangeOnlineManagement; Get-Module ExchangeOnlineManagement
Run the following command to update the EXO V2 module to latest version that’s available in the PowerShell Gallery: Update-Module -Name ExchangeOnlineManagement Enter Y to accept the license agreement.Note: If you receive the following error related to the PowerShellGet module, see Step 1 in the previous Install the EXO V2 module section to update the PowerShellGet module to the latest version.The specified module ‘ExchangeOnlineManagement’ with PowerShellGetFormatVersion ‘<version>’ is not supported by the current version of PowerShellGet. Get the latest version of the PowerShellGet module to install this module, ‘ExchangeOnlineManagement’.If you need to update the PowerShellGet module, be sure to close and re-open the Windows PowerShell window before you attempt to update the ExchangeOnlineManagement module.
To confirm that the update was successful, run the following commands:Import-Module ExchangeOnlineManagement; Get-Module ExchangeOnlineManagement
You can download the PowerShell command-lets today from:
Office 365 is continually evolving, expanding and improving – meaning new capabilities and opportunities, alongside the need to support adoption and manage change on an ongoing basis. Over the years I have been asked to do lots of On Premise current state assesments to help customers plan and check to ensure that their infrastructure is running optimally and meets current, and future, requirements. Recently however I have noticed an incline in requests from customers who want the same current state assesment for Office 365.
Whilst doing a bit of googling to see if there were any reporting tools that could ensure I capture key information on our customers tenant I was amazed at what I found, the following tool can be downloaded for FREE from Microsoft Technet and it ticks all the boxes:
Below are some screenshot from within the reporting tool:
What Can the Tool Do?
The tool provides detail reports on the following areas of Office 365
Azure Active Directory (43 reports)
Security Reports (22 Reports)
Exchange Online (99 reports)
SharePoint Online (35 reports)
OneDrive for Business (11 reports)
Skype for Business (22 reports)
Yammer (20 reports)
Microsoft Teams (16 reports)
General Office 365 Reports (9 reports)
Reporting Capabilities Highlights
This Office 365 Reporting tool comes with advanced reporting capabilities which make tedious reporting task to an easier one.
Automatic Schedule – Schedule one or more reports to run automatically at the configured time and delivered straight to your preferred mail-ids.
Rich Filters – Apply filter on any columns to see only the required information and save the filter for future use.
Easy Customization – Allow you to easily customize the reports by rearranging, adding or removing the columns and its size.
Report Export – Ability to export the reports to CSV, PDF, HTML, XLS or XLSX.
For me this tool will help me put together usefull documentation that we can present to customers and hopefully help plan a way forward with something that customers have aready invested in, I believe this FREE tool will help customers decide on a stratagy to develop their Office 365 utilisation for the better.
I have recently been working on a project to move nearly 2000 users from one Office 365 tenant to another. You may say simple, there are plenty of third party tools out there that will do that for you, but what about if the customer has not budgeted for the extra cost for these tools…. What do you do?
Now in this solution we had to purchase a very cost effective tool and a SSL certificate for the Exchange Server. The costs for these were no where near the costs of all of the well known tools from BitTitan and Cloud Migrator. we were quoted $6 per user by BitTitan as it was education or for normal businesses we were quote $14 per user. So as you would expect approx 2000 licenses at $6 each works out very expensive for an unexpected cost.
The tool we used was called Systools OneDrive Migrator and as you can see the tool cost starts from $99. We ended up paying $1 per user for this product. So a massive saving on the total cost of the tool from other competitors.
Before you deploy the On Premise Exchange Server you need to make sure your AD infrastructure is in good shape and able to support the deployment of Exchange 2016, so you need to ensure that the Forest and Domain Functional Levels are at least Windows Server 2008 R2
Before you begin to install Exchange Server 2016 you will need to install the Windows Server Roles and Features… Below is the PowerShell to ensure that all Windows Features are deployed:
A successful Exchange Installation will look like this:
Stage 2 – AAD Connect
A Guide for deploying AAD Connect can be found here
Key things to take into consideration are to ensure the following:
1, The AD Account UPNs match that of the email address of the user
2, When you deploy AAD Connect the following options must be chosen in order for the Exchange Hybrid to work correctly:
Stage 3 – Update all the users in Active Directory to have some Exchange attributes
The first thing you need to do is collect information about the online mailbox that you are looking to move. The information you need is the Mailbox Alias The User Principal Name and the Mailbox Guid. To get this information and output it to a CSV file run the following script in your Exchange Online Shell.
Once you have exported the above information you will need to move over to you On Premise Exchange Server and the Exchange Management Shell and run the following command that update all of the Active Directory objects with the required Exchange Attributes:
When you go into the Exchange Management Centre and look at the mailboxes you will be able to see all of your Exchange Online Mailboxes listed in your On Prem Exchange Server.
Stage 4 – Migrate mailboxes to Exchange 2016
Prepare the Hybrid Configuration
Details for configuring and Exchange Hybrid based on your on prem Exchange Server can be found here:
Stage 5 – Migrate mailboxes to the other Office 365 Tenant
Re point the Hybrid connection to the new Office 365 Tenant
All the hard work would have been done in the previous section about creating the hybrid. – all you need to do here is re run the hybrid configuration wizard and point it at the new Office 365 tenant.
Migrate mailboxes to Office 365
Steps to move mailboxes back to Office 365 can be found here
Stage 6 – Preparing OneDrive For Business for Migration
In order for us to be able to migrate data from OneDrive for business we will need to configure user interpretation on all of the users OneDrive sites. To do this the following steps need to be followed:
Assign eDiscovery permissions to OneDrive for Business Sites – Follow this guide from Microsoft:
Once this has been done, the user that will be used to the data migration will have sufficient access to the users OneDrive for Business sites.
Stage 7 Migrating OneDrive For Business to the new Tenant
This stage is rather like the previous one. However you will need to ensure that all the users OneDrive sites have been provisioned, unfortunately just by allocating a license to the user does not automatically provision, so there is a script that needs to be run in order to force the provisioning to take place. This also takes some time to do depending on how many users there are.
1, Provision OneDrive For Business Sites in new Tenant
3, Run the Systools Migration Tool to move the data between the tenants. – Make sure your CSV files that are created with this tool match the users up correctly, as it will be very easy to mix up the user source and destination. – we don’t want users to get the wrong data in their OneDrive sites.
Some companies I deployed Exchange or Office 365 would like to be able to view readable information in everyone’s calendar by default you only get Free or Busy information. The following script changes the default calendar permissions for ALL Users folders to Reviewer – This gives you readable / not editable information.
Senior management sometimes have PA’s that will need delegate access to their calendar, this this will include view calendar items that are marked as private.
To Set the delegate to view private items in the calendar
Wow, time flies when you are having fun….I can’t believe it has been 7 months since my last post.
So since January I have been really busy with numerous projects revolving largely around Office 365 and Exchange. I have picked up some useful knowledge which I will write about here in the coming weeks.
This post is dedicated to something new to me – G-Suite to Office 365 – What a ride this has been! Let me explain how I managed to get it all to hang together and get the two services to exist together during the migration and testing phases.
EMAIL Co Existence / Routing between O365 and G-Suite
This was the tricky bit, how could we get users to co-exist in different services whilst we undertake testing and migrations? There is no connector or hybrid solution like there is with Exchange. We did not want to cut over all the users at the same time – this had to be a phased migration over to Office 365. We are also using MimeCast for SPAM and Relay protection so we need Google & Office 365 to send outbound via Mimecast without any mails getting blocked. Here is how we did it:
Office 365
Office 365 needs to be forwarding mail onto a domain that G-Suite knows about and the users mailboxes need to have an alias address for office 365 to forward onto.
The steps are as follows:
Add Domain Domain A with MX Record
Add secondary email address for each user. This needs to be set to: user@domainA.com
For users that are not yet in Office 365 we need to configure the Accepted Domain as an Internal Relay in Mail Flow in Exchange Online Admin Centre
Then we create a connector back to G-Suite for any address that does not live in O365 yet. Doing this tells Exchange Online to send the email to the recipient over in G-Suite.
We then stumbled across another minor problem. In order for the Email Data to be migrated into the new Office 365 users mailbox, we need to activate the license. In doing this creates a Office 365 mailbox so then Office 365 thinks the user is now happily working from Office 365. “WRONG”!!! The user still lives in G-Suite until the migration is completed. So in order for the users in Office 365 to send to a user in G-Suite who’s mailbox is provisioned in O365 we have need to create another forwarder back to G-Suite until the migration is completed. How to do this in bulk is in a following section in the blog post. – Adding Contacts to Office 365.
G-Suite
G-Suite needs to have a forwarder configured that the Tenant does not have the domain registered to. If you register a domain with Google it treats all SUB domains as internal as well, so a completely new unregistered domain is required to forward any Office 365 bound mail to.
In order for Gmail to send a message to a forwarding address, the address needs to be verified. So here is a way to forward to an address that is not verified (added to the G-Suite Tenant):
You will need to apply mappings (aliases) to recipient addresses on messages received by your domain. You can map multiple individual recipient addresses (a maximum of 2,000 entries) to other addresses. An individual address can map to a maximum of twelve addresses.
This is a basic routing concept, sometimes called a virtual user table, that’s frequently used in mail routing situations to redirect mail from one address to another. By using this setting you don’t need to create individual routing settings for each address mapping.
Configure the Recipient address map setting for your domain:
From the Admin console Home page, go to AppsG SuiteGmailAdvanced settings.Tip: To see Advanced settings, scroll to the bottom of the Gmail page.
At the top of the page, ensure that the top-level org is highlighted.
Scroll down to the Recipient address map section, or type Recipient address map in the search box:
If the setting’s status is Not configured yet, click Configure (the “Add setting” dialog box displays).
If the setting’s status is Locally applied or Inherited, click Edit to edit an existing setting (the “Edit setting” dialog box displays).
Enter a short description that will appear within the setting’s summary.
Under Messages to affect, select All incoming messages or Only external incoming messages.
Scroll down to Routing options, and select Also route to original destination to send a copy of the message to the new address and also deliver it to the original recipient.
Note: If you don’t select this option, the message is only sent to the new address.
For example, jensmith@solarmora.com is in the address map and the new address is jensmith@gmail.com. If the checkbox is checked, both jensmith@solarmora.com and jensmith@gmail.com will receive a copy of the message. If the checkbox is unchecked, then only jensmith@gmail.com will receive the message.
Enter address mappings in the box.
Each mapping must include two addresses on a single line, separated by a comma. Place the map-to address after the comma. In the following example, davidb@solarmora.com is the map-to address:
When you’re finished making changes, click Add setting or Save to close the dialog box. Note: Any settings you add are highlighted on the “Email settings” page.
Click Save changes at the bottom of the “Email settings” page.
When you’re finished, click Add Setting (at the bottom of the dialog box).
Click Save changes (at the bottom of the “Email settings” page) to confirm your changes.
It can take up to an hour for changes to propagate to user accounts. You can track changes in the Admin audit log.
Adding Contacts to Office 365
First of all you will need a CSV file like the one in the image below ensuring the column headers match:
When you have created your list of new Contacts that you need to create you can then import these into Office 365 using the following Powershell Commands:
We then had to update all the Office 365 mailboxes to use the forwarding address to send mail back to G-Suite using the following PowerShell and CSV file:
So when adding the mailboxes in Office 365 be default the users email addresses were the onmicrosoft.com domain. This was happening because there were no On Premise Exchange Server therefore no Proxy addresses recorded in Active Directory. We then had to add all of the email address alias’s to the proxy addresses using PowerShell. The next few commands are how we did this.
Export the SamAccount and Existing Email details
Import-Module ActiveDirectory
# Delete file if it exists
$FileName = "C:\temp\user.csv"
if (Test-Path $FileName)
{
Remove-Item $FileName
}
Get-Aduser -filter * -Properties * |
Select SamAccountName,mail | export-csv $FileName
Once you have a list of users with the correct list of Alias addresses I then ran the following PoweShell to update all of the proxy addresses
Navigate to Apps | G Suite | Gmail | Advanced Settings.
Click on the Hostsbutton.
Click on the Add Route button.
Enter a Route Name (e.g. Mimecast Outbound Host).
Select Multiple Host and enter the Mimecast Outbound Hostnames for your Mimecast region. Both must be marked as primary. See the “Outbound Send Connectors section of the Mimecast Gateway page for full details.
Click on the Save button.
Click on the Add Route button.
Enter a Route Name (e.g. Internal Sending Host).
Select Multiple Host and enter the Google Apps MX Records (ASPMX.L.GOOGLE.COM. and ALT1.ASPMX.L.GOOGLE.COM).
Click on the Save button.
To configure routing rules:
Click on the General Settings tab.
Navigate to the Routing section.
Click on the Configure button.
Select the Outbound option in the “Messages to Affect” section.
Select the Change Route option in the Route section.
Select the Route Name created in step 5 of the “Preparing Your Outbound Hostname” section.
Click on the Add Setting button.
Click on the Add Another button.
Select the Internal | Sending option in the “Messages to Affect” section.
Select the Change Route option in the Route section.
Select the Route Name created in step 9 of the “Preparing Your Outbound Hostname” section.
Click on the Add Setting button.
Office 365
Log in to the Office 365 Administration Console.
Select the Admin | Exchangemenu item.
Select the Mail Flow | Connectors menu item.
Create a Connector.
Complete the New Connector – Select Your Mail Flow Scenario dialog as follows:
Field
Description
From
Select “Office 365” from the drop down list.
To
Select “Partner Organization” from the drop down list.
Select the Next button.
Complete the New Connector – New Connector dialog as follows:
Field
Description
Name
Enter a name for the connector.
Description
Enter a description for the connector.
Turn It On
Select this option to enable the connector.
Select the Next button.
Select the Only When Email Messages are Sent to These Domains option.
Select the icon to add the recipient domains that should use this connector.
Enter a value of *to route all outbound emails through us.
Select the OK button.
Select the Next button.
Select the Route Email Through These Smart Hosts option.
Select the icon to add your region’s smart hosts.
Region
Office 365 Account Hostnames
Europe (Excluding Germany)
eu-smtp-o365-outbound-1.mimecast.com
eu-smtp-o365-outbound-2.mimecast.com
Germany
de-smtp-o365-outbound-1.mimecast.com
de-smtp-o365-outbound-2.mimecast.com
America
us-smtp-o365-outbound-1.mimecast.com
us-smtp-o365-outbound-2.mimecast.com
South Africa
za-smtp-o365-outbound-1.mimecast.co.za
za-smtp-o365-outbound-2.mimecast.co.za
Australia
au-smtp-o365-outbound-1.mimecast.com
au-smtp-o365-outbound-2.mimecast.com
Offshore
je-smtp-o365-outbound-1.mimecast-offshore.com
je-smtp-o365-outbound-2.mimecast-offshore.com
Select the Save button.
Select theNext button.
Select the following options:
Always use Transport Layer Security (TLS) to Secure the Connection (recommended)
Issued by a trusted certificate authority (CA)
Select the Next button.
Select the Next button.
Add an Email Address of a recipient from a domain external to your organization.
Select the Validate button.
Select the Save button once Office 365 has successfully validated your settings.
So our experience with the Cloud Migrator APP has been interesting. Initially we started to use the Cloud Migrator Go SaaS application which was reasonably simple to configure following the guides provided by Cloud M. However we soon realised there were speed issues when moving data between G-Suite & O365. The issues are caused by the API’s between GSuite and O365 being limited. There is nothing we or Cloud M could do to improve the migration speed between the two services.
We then switched to the Cloud Migrator App which you install on your own dedicated server On Premise – in our case we used a Virtual machine in VMWare. Once configured we were able to fire up numerous Servers to run Cloud Migrator having a number of migration batches running at the same time and our Data throughput seemed to be 4x that of the cloud Migrator Go SaaS option.
All in all the customer is now running Co Existence of Office 365 and G-Suite. Mail is flowing and users are happy. We intend to complete the migration to Office 365 in the coming weeks. I decided to write this post as there does not seem to be many guides out there to help you migrate from G-Suite to Office 365. Hopefully if you read this it will help you on your projects.
One of my recent projects was to implement a new Highly Available Exchange 2016 environment for a customer who was upgrading from Exchange 2010. When Exchange 2016 was in place, we then had to create hybrid to Office 365. Below are some really useful PowerShell Commands I used during the implementation.
So after a successful deployment of Exchange 2016 the next step was to create a hybrid to Office 365 Exchange Online, Simple as Exchange 2016 was “Born in the cloud” according to Microsoft. NOT SO!!! – I downloaded the latest version of Exchange 2016 which at the time was CU7, but when configuring the hybrid it would just sit at adding Federated Domain.
A bug slipped into Exchange 2016 CU7 which prevents the HCW from completing. The HCW fails to get past the domain ownership validation:
No matter how hard you try, you can’t get past this screen.
Fortunately CU8 was release 19th December 2017 – So I spent the next day patching my newly installed Exchange environment. – then completing the Hybrid configuration.
Well, here is a nice little feature that I was unaware of until today…. A handy way to inform your users on support information for Microsoft Office 365.
As an Office 365 admin, you can streamline user support by adding customised contact information to the help pane. Users in need of support will be able to access your organisation’s custom support contact info with a single click of the help icon.
Create the custom help desk card
NOTE: To create a custom help desk card, you must be a global admin for Office 365 and have a license to Exchange Online. Learn how to assign licenses in Office 365 for business.
Create the custom help desk card in the admin center
3. Choose the settings icon, and then choose Organization profile.
4. Next to Provide customized help desk contact info, choose Edit.
5. Turn on the Help desk card.
6. As an admin, you decide what kind of contact information you want to give users. The title and at least one form of contact information are required. Select what you want to display, and fill out the appropriate info.
o Custom title: Enter a title that clearly indicates your intent, like “Contoso help desk” or “Need help?”
o Help desk phone: Enter the phone number users should call to talk to a tech support agent at your organization. Be sure to include any prefixes that may be needed to complete the call.
o Help desk email: Enter the email address for your support department.
o Help desk URL: If your support department has an internal or public website with helpful tools and resources, enter its name and the associated URL.
7. Choose Save.
To see your new customized help desk card, sign out and back in again. We recommend you test the links on the card as soon as you sign back in. Your users will be able to see the card the next time they sign in.
Last year, Microsoft released a product called Bookings to customers in the U.S. and Canada, introducing an easy way for small businesses to schedule and manage appointments with their customers. Microsoft have recently announced that they are beginning to roll out the service to Office 365 Business Premium subscribers worldwide. based on user feedback, they are bringing several new features to Bookings as well.
Add your Office 365 calendar to Bookings—Connect your Office 365 calendar to Bookings, so that the times you are busy will automatically be blocked in your public Booking page.
Add buffer time before and after your appointments—Do you need prep time before or after an appointment? Adding buffer time to a service automatically blocks that time in your Booking page too.
Bookings apps for your iOS and Android phone—Now you can book an appointment, contact a customer or check a staff member’s appointments while away from the office.
Customize your Booking page—We added more color customization options, so you can better personalize your Booking page.
These new capabilities will start showing up automatically in Bookings in the coming weeks. Let’s take a detailed look at what’s new.
Add your Office 365 calendar to Bookings
One of the top pieces of feedback we’ve heard is that you want to be able to add events from your Office 365 calendar to Bookings. So, we added integration between these calendars to help you avoid booking customer meetings during the time you’ve set aside for personal appointments, staff and partner meetings or other aspects of running your business.
To add Office 365 calendars to Bookings, click the Staff tab on the left navigation panel. On the Staff details page, select the Events on Office 365 calendar affect availability checkbox.
Add Office 365 calendar events to Bookings.
Once you activate this option, the system automatically blocks busy times on the Bookings calendar and on the self-service Booking page your customers see, so that you won’t get double-booked. Similarly, so your staff doesn’t get double-booked, you can also add their Office 365 calendars.
Add buffer time between appointments
Some services can be provided through back-to-back appointments. But another top piece of feedback you gave us was that many of your services require travel, prep and/or set-up time beforehand, and clean-up and travel time once the service was delivered. For customers with these needs, we added buffer times to give you more options to customize the services you deliver.
To add buffer times, click the Services tab in the left navigation column and either edit a current service or create a new one. Turn on the toggle below the Buffer time your customers can’t book and you will get buffer time selections that can be applied before and after the service appointment. These are times your customers can’t book an appointment with you before and after an appointment.
You can turn on the “buffer time” option in the Services tab.
Apps for iOS and Android
We know it’s essential for you to keep up with your business while you are away from a desk, so we built mobile apps that let you manage your bookings and staff, or access your customer list while you’re on the go.
After you download the Bookings app on iOS and Android, you can use your phone to:
View and manage your Bookings calendar.
Create and edit bookings.
See real-time availability and whereabouts of your staff.
Respond to customers with bookings quickly and easily.
Get directions to your next booking.
Access your customer list.
Customise your Booking page
Your Booking page should look and feel like an extension of your business, and it needs to positively reflect your brand.
To help you achieve this, we added options to customize it. For example, you can choose your main color for your Booking page from a color palette, and choose whether you’d like to show your business logo.
To customise your page, click Booking page in the left navigation list and select the color you want. If you don’t want your logo to be displayed, uncheck the Display your business logo on your booking page checkbox. Once you are done, simply click Save and publish.
Use the Booking page tab to customize your Booking page. Remember to click Save and publish to keep your changes.
How to get started with Bookings
Bookings is included in all Office 365 Business Premium subscriptions, and getting started is easy. To simplify the work of customer scheduling for your business, just sign in to Office 365 and click the Bookings tile on the App Launcher. If you don’t see the Bookings tile, we may still be in the process of rolling out the service in your region—so check back a bit later. If you need more help, the article “Say hello to Microsoft Bookings” provides a quick overview of how to use Bookings.
Once you are signed in to Office 365 you can find the App Launcher on the top left corner.
Bookings is designed to delight your customers, simplify scheduling and free time for you to be on top of your business wherever you are. Your feedback has been extremely useful; please keep it coming by clicking the feedback links found on the Bookings home page.
Microsoft intend to bring Bookings to E3 and E5 customers in the near future
My adventures within Microsoft Office 365 continue… another new feature to Microsoft Office 365 Power Apps.
Back in November 2016, Microsoft released for general availability Microsoft Flow and PowerApps. These tools will give users the power to enable the automation of workflows and the building of custom apps, and will also ease and expedite the creation of applications without the need for complex custom software development.
Microsoft Flow is a new workflow automation solution that can be used to tap application and service data, making it easy to combine different services. Microsoft Flow connects more than 35 services, including SharePoint, OneDrive, Slack, and Twitter, so that users can perform actions such as sending notifications, pushing data into Excel, sending OneDrive files to SharePoint sites, automatically copying files from Dropbox to their SharePoint document library, and creating simple workflow approval tracking. Along with this, business users will be able to use Microsoft Flow to utilise pre-built templates and create their own flows in a visual designer that can work anywhere on the web.
Below is a short video detailing how Flow will be able to automate your repetitive daily tasks: