<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Synchronisation on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/synchronisation/</link>
    <description>Recent content in Synchronisation on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 06 Jan 2014 13:02:55 +0000</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/synchronisation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Update Obsolete User Principal Names in Office 365 Windows Azure Directory</title>
      <link>https://janikvonrotz.ch/2014/01/06/update-obsolete-user-principal-names-in-office-365-windows-azure-directory/</link>
      <pubDate>Mon, 06 Jan 2014 13:02:55 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2014/01/06/update-obsolete-user-principal-names-in-office-365-windows-azure-directory/</guid>
      <description>&lt;p&gt;It could happen that the directory sync service (DirSync) doesn&amp;rsquo;t sync the users UserPrincipalName correctly.&lt;/p&gt;&#xA;&lt;p&gt;I had an issue where the UserPrincipalName from a user in the Office 365 windows azure directory has been made based on the user&amp;rsquo;s sAMAccountname. This wouldn&amp;rsquo;t be problem if as long the sAMAccountname is the as same as the UserPrincipalName, but as you can guess this is not everywhere the case.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
