With Microsoft introducing MS-Teams earlier this year, the team are working on rolling out new features. Outlook add-in being one of them. It is now in general availability. This enables users to host/join a team meeting from Outlook client. There is no separate installation required for this. Follow the steps below:
- Download MS-Teams desktop client.
- Login using your credentials and logout.
- Make sure you are using the latest version on Outlook 2016
- Start MS-Teams and login again using your credentials.
- Start Outlook and you should see the Join Teams Meeting option in the New Items menu.
If you haven’t started using MS-Teams to collaborate with your colleagues, feel free to get in touch.
Recently while provisioning a huge SharePoint 2016 farm (around 70 server) on MS-Azure with 3 Office Online servers, I came across some cross domain issues with Office Online.
We had provisioned all the four environments (development, test, pre-prod and production) on Azure but on two different domains and here come the real complexity 🙂
The users who would be accessing the site were using laptops which were on the AD domain; for example, AD\anandsharma being their account ID.
Accessing the development and test URL’s with such devices required appending the domain name after the SharePoint site url to resolve the DNS. For example: http://sharepointsite-dev.ppad
Now while setting up Office Online servers in such cases has a big caveat!!
So let’s say my Office Online server’s load balancer (as in our case) has the internal URL as http://sharepointsite-dev-oos and everything is configured according the the following technet article – https://technet.microsoft.com/en-us/library/jj219455(v=office.16).aspx
In such a scenario, the cross domain dns resolving will not work.
Hence while configuring the Office online server, you must append the domain name to the internal url property when configuring the new farm.
Configuration on the Office Online Server (Development)
Import-Module -Name OfficeWebApps
New-OfficeWebAppsFarm -InternalURL "http://sharepointsite-dev-oos.ppad" -AllowHttp -EditingEnabled
Configuration on the SharePoint Web Front End (Development)
New-SPWOPIBinding -ServerName "sharepointsite-dev-oos.ppad" -AllowHTTP
Set-SPWOPIZone -zone "internal-http"
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$Farm = Get-SPFarm
Hope this helps anyone struggling with cross domain configurations.
There have been instances when the SharePoint super users behaves adventurous and test SharePoint capabilities. As a result of their playing around and testing the system, they create entries here and there and then forget about them completely. One such user came to me with an error “Something went wrong” (default SharePoint error message) while he was trying to add content type to the document library. Continue reading “Error on adding content types to document library”
So we want to add few custom links to the Delta suite bar within Office 356. You can either add it to the Script Editor webpart to add these links for single page or add it to the master page if you want so.
var addLinks = "<div class='o365cs-nav-O365LinksItem'><div><a title='Google' class='o365button o365cs-nav-navItem o365cs-nav-workloadLink o365cs-spo-topnavLink o365cs-topnavLink' id='O365_MainLink_ShellMail' role='menuitem' aria-disabled='false' aria-selected='false' aria-label='Google' href='http://google.co.uk'><span>Google</span><div class='o365cs-activeLinkIndicator o365cs-nw-b' style='display: none;'></div></a></div><div style='display: none;'></div></div>";
addLinks += "<div class='o365cs-nav-O365LinksItem'><div><a title='Bing' class='o365button o365cs-nav-navItem o365cs-nav-workloadLink o365cs-spo-topnavLink o365cs-topnavLink' id='O365_MainLink_secondLink' role='menuitem' aria-disabled='false' aria-selected='false' aria-label='Bing' href='http://bing.co.uk'><span>Bing</span> <div class='o365cs-activeLinkIndicator o365cs-nw-b' style='display:none;'></div></a></div><div style='display: none;'></div></div>";