Following my previous post related to the availability of the multiple factors authentication preview for Office 365, here is an additional one to detail the management.
Once you have enabled multi factors authentication (follow this post http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=524), you can manage additional settings such as viewing usage reports, download the SDK or configure blocked/bypassed user or fraud alert.
I just being notified that I have been awarded as Microsoft Community Contributor on Office 365 for my answers on Office 365 Community forums.
Microsoft has released a preview of the two factor authentication feature for Office 365, Windows Azure, Windows Intune or Dynamics CRM Online.
NOTE once enabled, the user will not be able to sign-in to non-browser clients like Outlook, Lync or PowerShell
You must enabled Push notification to be able to add an account
Starting today, Office 365 customers with Enterprise plan can enable Yammer as the default social network in replacement of the SharePoint newsfeed.
To do so:
Once done, the Newsfeed link available on top is changed to Yammer
End user may receive a request to confirm to go to Yammer
Then you will be redirected to your Yammer site.
As part of the latest post about directory synchronization with Office 365, here is a small trick to manage the schedule for directory synchronization.
This is not new with the latest release.
By default, DirSync is synching your AD with Office 365 every 3 hours. But you may want to manage this schedule in order to do it more or less frequently. Off course, you still have to ability to run a PowerShell script to force the synchronization .
So, the DirSync schedule settings is located in the Microsoft.Online.DirSync.Scheduler.exe.config file stored in the installation folder of DirSync (default is C:\Program Files\Windows Azure Active Directory Sync) – NOTE: if you are still using an older version of DirSync, the folder name may be different to Microsoft Online Directory Sync
To change the schedule from running every 3 hours to what you want, just open the file and change the value of SyncTimeInterval.
After changing this settings you have to restart ForeFront services in order to take into account the new value of the schedule time.
As you may already know there 2 way to manage user accounts on Office 365:
The latest release of DirSync is now including a long waited feature: password synchronization
This was a long wait feature as until now, there was no way to synchronize your on premise password except by implementing ADFS which is NOT password synchronization but redirecting authentication processes to your on premise AD; this means in case of your ADFS is not available, there is no way to access your Office 365 data.
So, the new DirSync release now offers to synchronize your AD password with your Office 365 account.
Go to http://go.microsoft.com/fwlink/?LinkID=278924 to download the latest release (only available in 64 bits version).
The install process is mainly the same than previous version of DirSync – if you already had DirSync installed you have to uninstall it before; don’t worry, you will not loose your existing account and the next sync will not be a full one . You can check this post for the installation process http://blog.hametbenoit.info/Lists/Posts/ViewPost.aspx?ID=260
You may have a .Net Framework error related to security permission; just right click on the installation file and choose Run as administrator
Once installed, during the configuration process you will have a new step called Password Synchronization; if you want to enable it, just check the box
To know more about this new feature, go to http://technet.microsoft.com/en-us/library/dn246918.aspx
As you may already know, if not this is done , you can now embedded some HTML code on your SharePoint pages (available on SharePoint 2013 and SharePoint Online); especially on blog post.
To do so, just create a new blog post (or page) and use the Insert tab and Embed Code button.
However, there is some security settings associated with this option.
I ran onto an issue when I tried to embedded a Slideshare presentation I just uploaded earlier.
This HTML cannot be inserted because this type of content is not allowed.
After digging a little bit on this issue, the security settings associated with the embedded code option is available at the Site Settings\Site Collection Administration\HTML Field Security option
When you go there, you can allow/disallow embedded code and then if allowing, manage from which domain embedded code is allowed. By default, there is only YouTube, Bing, Skydrive and Office.
I have uploaded a presentation about right management services on Office 365, called Azure Active Directory Right Management (AADRM).
With BPOS and the first version of Office 365, Microsoft has provided a web tool (Speed Test) to assist customer to determine if their internet connection can support Microsoft Online services, from messaging to collaboration [covering Exchange Onlnine but more important Lync as it may consume important bandwidth]. This tool was available from www.microsoftspeedtest.com
Since few months, this site is no longer available and many Office 365 customer (existing or potential) as well as consultant implementing Office 365 have no tool to evaluate the impact of Microsoft Online services on their internet connection.
Fortunately, there is another tool available – initially covering only Lync (Lync Online Transport Reliability IP Probe - TRIPP), can provide a good replacement.
Unfortunately, there is no global URL as it was the case with Speed Test; this means you have to use the URL the most appropriate accordingly to the datacentre used for your Office 365 tenant:
That’s said, how it works??
As you may already know, Microsoft has announced few months ago the end of some ForeFront products line, including ForeFront Protection the antivirus solution for Exchange, SharePoint and Office Communication Server (yes, Lync never had any updates while it has been long waited since Lync 2010).
As part of this, you may also have read some information about the fact that ForeFront Protection for SharePoint may be installed on top of SharePoint 2013 as no change have been made at the SharePoint antivirus API levels (see the well famous http://www.harbar.net/archive/2013/02/22/Antivirus-and-SharePoint-2013.aspx)
I had a customer which already have ForeFront Protection for SharePoint which wanted to use it for their new SharePoint 2013 implementation. So we tried and… we failed.
Indeed the setup program for ForeFront Protection is looking for some prerequisites which have been (off course) installed, except SharePoint Foundation 2010.
This is now a final conclusion that ForeFront Protection can’t be installed on top of SharePoint 2013.