Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: https://blogs.msdn.microsoft.com/pandrew/feed/

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  3.  version="2.0">
  4.  <channel>
  5.    <title>Paul Andrew</title>
  6.    <atom:link
  7.      href="https://docs.microsoft.com/archive/blogs/pandrew/feed.xml"
  8.      rel="self"
  9.      type="application/rss+xml" />
  10.    <link>https://docs.microsoft.com/archive/blogs/pandrew/feed.xml</link>
  11.    <description>Technical Product Manager for Office 365 at Microsoft</description>
  12.    <lastBuildDate>Tue, 16 Apr 2019 05:22:03 GMT</lastBuildDate>
  13.    <language>en-US</language>
  14.    <sy:updatePeriod>hourly</sy:updatePeriod>
  15.    <sy:updateFrequency>1</sy:updateFrequency>
  16.    <item>
  17.      <title>GA - Partner Center SDK and REST API Live now</title>
  18.      <link>https://docs.microsoft.com/archive/blogs/pandrew/ga-partner-center-sdk-and-rest-api-live-now</link>
  19.      <pubDate>Fri, 11 Mar 2016 12:15:50 GMT</pubDate>
  20.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  21.      <guid
  22.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2016/03/11/ga-partner-center-sdk-and-rest-api-live-now/</guid>
  23.      <description><![CDATA[We just announced&nbsp;the general availability of the Partner Center SDK and REST API. The Partner...]]></description>
  24.      <content:encoded><![CDATA[<p>We just announced&nbsp;<strong>the general availability of the Partner Center SDK and REST API</strong>. The Partner Center SDK makes it easy for Microsoft Cloud Solution Provider partners to integrate their sales systems with the Microsoft Partner Center system which powers the Cloud Solution Provider (CSP) program. Having integration with Microsoft systems means the CSP partner can focus on their business instead of on processing transactions manually.</p>
  25. <p>The Partner Center SDK includes:</p>
  26. <ol>
  27. <li>Microsoft CSP Managed API libraries for use with Visual Studio 2015 or Visual Studio 2013.</li>
  28. <li>Sample web application using Managed CSP APIs to quickly configure and publish a website.</li>
  29. <li>Sample code for service applications or console applications using the Managed APIs.</li>
  30. <li>Full documentation and training material, with MSDN forums and other support options.</li>
  31. <li>Partner Center REST APIs which can be used by developers who have other development environments and other programming languages.</li>
  32. </ol>
  33. <p>&nbsp;</p>
  34. <p>&nbsp;<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/2620.VS.JPG" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/2620.VS.JPG"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/2620.VS.JPG" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/2620.VS.JPG" alt="" border="0" /></a></p>
  35. <p><em>The Partner Center SDK managed API sample code</em></p>
  36. <p><em><br /></em></p>
  37. <p>&nbsp;<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/1565.pcsdk-webapp.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/1565.pcsdk_2D00_webapp.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/1565.pcsdk-webapp.png" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/1565.pcsdk_2D00_webapp.png" alt="" border="0" /></a></p>
  38. <p><em>The Partner Center SDK sample web application</em></p>
  39. <p>&nbsp;</p>
  40. <p>New functionality in the Partner Center SDK includes a direct API to list customers, an API to list available offers, the ability to validate a new tenant name, to validate a VARs MPN ID, to raise and manage support tickets, to access invoice details, to access Azure rated usage and much more. With the Partner Center SDK, you get identity token management, network connection management, and a Managed API object collection interface.</p>
  41. <p>Partners who use the CREST and Graph APIs today can integrate the new Partner Center REST APIs with their existing code. We will continue to support the CREST APIs while partners are still using them. Moving over to Partner Center SDK provides the additional functionality available and in sync with the Partner Center, easy integration via the Managed API, the new sample code and training, and access to future Microsoft investment in the Partner Center SDK.</p>
  42. <p>To get started or get more information about Partner Center SDK and API, go to <a href="https://partnercenter.microsoft.com/partner/developer">https://partnercenter.microsoft.com/partner/developer</a>.</p>]]></content:encoded>
  43.    </item>
  44.    <item>
  45.      <title>Getting Started with the Cloud Solution Provider APIs</title>
  46.      <link>https://docs.microsoft.com/archive/blogs/pandrew/getting-started-with-the-cloud-solution-provider-apis</link>
  47.      <pubDate>Wed, 26 Aug 2015 13:59:00 GMT</pubDate>
  48.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  49.      <guid
  50.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2015/08/26/getting-started-with-the-cloud-solution-provider-apis/</guid>
  51.      <description><![CDATA[If you're a Cloud Solution Provider (CSP) partner, you have many options for transacting your...]]></description>
  52.      <content:encoded><![CDATA[<p>If you're a Cloud Solution Provider (CSP) partner, you have many options for transacting your customers orders with Microsoft. In this post I'll walk through getting started with the CSP Application Programming Interfaces (APIs) and point you to some resources for learning more about them.</p>
  53. <h2>Do you need to use APIs for Integration?</h2>
  54. <p>Most partners who undertake CSP API integration work do so because they have an existing customer portal where their customers purchase from them and they want to have direct integration between that portal and Microsoft. This would enable the partner to sell Microsoft commercial cloud services directly from their own portal through the CSP program. Here are some other&nbsp;options for selling through the CSP program.</p>
  55. <p><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/8168.Options%20for%20CSP%20transactions.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/8168.Options-for-CSP-transactions.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/8168.Options%20for%20CSP%20transactions.png" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/8168.Options-for-CSP-transactions.png" alt="" border="0" /></a></p>
  56. <ul>
  57. <li><strong>Code against CSP APIs</strong> -&nbsp;this is what I'll focus on below in the post</li>
  58. <li><strong>Use Partner Center web site</strong> - You can use the Partner Center web site that Microsoft provides, but your customers cannot access that so you have to place the orders for them</li>
  59. <li><strong>Panel Providers Prebuilt Portal</strong> - You can use a 'control panel' from an ISV who specializes in that and their software will access the CSP APIs on your behalf</li>
  60. <li><strong>Use a Distributors Portal</strong> - If you are a reseller working with a 2 tier CSP distributor then you would normally use the portal that the distributor provides</li>
  61. <li><strong>Hire Third Party Developer</strong> - The other way you can avoid coding against the APIs is to hire developers who can do it for you</li>
  62. </ul>
  63. <h2>Pre-requisites</h2>
  64. <div>
  65. <p>To be successful with the Cloud Solution Provider CREST APIs you should already have the following pre-requisites:</p>
  66. <ul>
  67. <li>Must be already on-boarded as a Cloud Solution Provider partner with access to <a href="https://partnercenter.microsoft.com">https://partnercenter.microsoft.com</a></li>
  68. <li>Have developers with experience using REST and JSON. All integration with the CSP APIs uses industry standards based REST and JSON message formats over HTTPS.</li>
  69. <li>Ideally developers should also have experience with Azure AD authentication and C#. It is not required to use C# since the APIs are available to any language which supports REST, however we provide the most comprehensive sample code in C# using Visual Studio 2015 and .NET Framework 4.5.</li>
  70. </ul>
  71. </div>
  72. <h2>Suggested Developer Training Plan</h2>
  73. <div>
  74. <p>Make sure you know who your software developers are who will be working on the integration project. Perhaps it is&nbsp;you. That person should review the available training material for working with the CSP APIs. We have links to this at the end of this document and it includes videos, MSDN documentation, MSDN forums FAQs, Code samples, and additional guidance.</p>
  75. <p>Once the introductory material is completed. Developers can get up to speed by working through these exercises:</p>
  76. <ol>
  77. <li>Request an integration sandbox account from Partner Center</li>
  78. <li>Request an App ID and client secret from Partner Center</li>
  79. <li>Build and run the CSP sample code from GitHub</li>
  80. <li>Build and run an Azure AD sample from GitHub</li>
  81. <li>Run a network trace and monitor the HTTP request and response</li>
  82. </ol></div>
  83. <h2>Example Integration Project and Development Sizing&nbsp;</h2>
  84. <div>Most partners who are integrating with the CSP APIs have an existing customer portal system that they sell to customers with. This customer portal may be linked to other internal systems such as an ordering system and a billing system. These existing systems need to work with an interface module that connects to the CSP APIs as shown in the following diagram.</div>
  85. <div>&nbsp;</div>
  86. <div><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/3583.Components%20of%20a%20Partner%20Architecture.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/3583.Components-of-a-Partner-Architecture.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/3583.Components%20of%20a%20Partner%20Architecture.png" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/3583.Components-of-a-Partner-Architecture.png" alt="" border="0" /></a></div>
  87. <div>&nbsp;</div>
  88. <div>A project plan for the integration work should include the following steps:</div>
  89. <div><ol>
  90. <li>Training time for developers on new tools and technologies</li>
  91. <li>Document system architecture of existing customer portal and associated systems</li>
  92. <li>Plan for CSP API integration points</li>
  93. <li>Review system architecture changes and improve</li>
  94. <li>Build out code proof of concept using CSP Integration Sandbox</li>
  95. <li>Review proof of concept code and improve</li>
  96. <li>Build solution</li>
  97. </ol></div>
  98. <div>To determine how much work will be required for this integration we recommend you have the team that would be doing the coding development time estimate the above integration work. Development teams should consider the integration interface module, any changes to your ordering and billing systems, any training or new technologies that they aren&rsquo;t familiar with and also time for integration testing.</div>
  99. <h2>Troubleshooting and Getting Help from Microsoft</h2>
  100. <div>
  101. <p>When troubleshooting a CSP API integration issue use some of the following guidance to identify and resolve the issue you are seeing.</p>
  102. <ol>
  103. <li>Become familiar with and handle all the error conditions from the CSP APIs. These are well documented in the MSDN documentation and most CREST API errors also return a JSON error structure with details of the error.</li>
  104. <li>Get the HTTP layer REST message request and response from the code that you are running and validate that against the sample messages in the MSDN documentation. You will also need these requests and responses logged in case you submit a post to the MSDN forum or to Microsoft support.</li>
  105. <li>Use the provided C# sample code and replicate the scenario with that. Do this even if you don&rsquo;t regularly use C#. Replicating the scenario in this simple code base will allow you to see what REST code is sent to Microsoft when the scenario is working. Of if it doesn&rsquo;t work with the sample code, you will have more information about the problem you are encountering.</li>
  106. <li>Post your request on the MSDN forums and include your scenario, your code snippet, and the HTTP log of your request and response. Make sure to remove your client secret from the sign-in request if you are including that to avoid security issues.</li>
  107. <li>You can use break fix support from the Partner Center web portal. This is available if you have something that you built and it was working, you changed nothing, and it appears that the Microsoft end of the integration stopped working. When you access break fix support it directs you to the Office 365 admin portal and be sure to select Partner Center APIs as the category of the support request.</li>
  108. <li>You can use MPN partner benefit support incidents for API on-boarding assistance to ask for help with doing API integration.</li>
  109. <li>You can also use Microsoft Premier Support hours to similarly ask for API on-boarding assistance.</li>
  110. </ol></div>
  111. <h2>CSP API Learning Resources Links</h2>
  112. <h3>Crest Commerce APIs</h3>
  113. <div>Purpose: For creating and editing new customers and for provisioning new subscriptions to those customers.</div>
  114. <div>
  115. <p>Intro onboarding video: <a href="https://youtu.be/8RRssasC2Ys">https://youtu.be/8RRssasC2Ys</a> &nbsp; <br />MSDN Documentation: <a href="https://msdn.microsoft.com/en-us/library/partnercenter/dn974944.aspx">https://msdn.microsoft.com/en-us/library/partnercenter/dn974944.aspx</a> &nbsp;<br />MSDN Forums: <a href="https://social.msdn.microsoft.com/Forums/en-US/home?forum=partnercenterapi">https://social.msdn.microsoft.com/Forums/en-US/home?forum=partnercenterapi</a> &nbsp;<br />Code samples: <a href="https://github.com/PartnerCenterSamples/Commerce-API-DotNet/">https://github.com/PartnerCenterSamples/Commerce-API-DotNet/</a> &nbsp;<br />MSDN Forums FAQ: <a href="https://www.microsoft.com/en-us/download/details.aspx?id=48218">https://www.microsoft.com/en-us/download/details.aspx?id=48218</a>&nbsp;&nbsp;</p>
  116. <h3>Azure AD Graph APIs</h3>
  117. <p><strong>Purpose:</strong> Partners can get a list of their customers, a list of each customer&rsquo;s users, can add and edit user details, can assign Office 365 seat licenses to specific users, and can add users to the admin group such that they can use the Azure management portal.<br /><br />MSDN Documentation: <a href="https://msdn.microsoft.com/en-us/library/azure/hh974476.aspx">https://msdn.microsoft.com/en-us/library/azure/hh974476.aspx</a> &nbsp; <br />MSDN Forums: <a href="https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=WindowsAzureAD">https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=WindowsAzureAD</a> &nbsp;<br />Code samples: <a href="https://github.com/AzureADSamples/ConsoleApp-GraphAPI-DotNet">https://github.com/AzureADSamples/ConsoleApp-GraphAPI-DotNet</a></p>
  118. <h3>Azure Rate card and Usage APIs</h3>
  119. <p><strong>Purpose:</strong> Partners can review near real time Azure service usage data from the Usage APIs and can lookup service costs per datacenter and date range with the rate card APIs.<br /><br />Overview: <a href="https://azure.microsoft.com/en-us/documentation/articles/billing-usage-rate-card-overview/">https://azure.microsoft.com/en-us/documentation/articles/billing-usage-rate-card-overview/</a> &nbsp;<br />MSDN Documentation: <a href="https://msdn.microsoft.com/en-us/library/azure/mt218998.aspx">https://msdn.microsoft.com/en-us/library/azure/mt218998.aspx</a> &nbsp;<br />Sample code: <a href="https://github.com/Azure/BillingCodeSamples">https://github.com/Azure/BillingCodeSamples</a>&nbsp;&nbsp;</p>
  120. <h3>Azure service provisioning APIs</h3>
  121. <p><strong>Purpose:</strong> Once the Azure subscription is setup you may want to provision specific services and administer them.<br /><br />MSDN Documentation: <a href="https://msdn.microsoft.com/en-us/library/azure/dn578292.aspx">https://msdn.microsoft.com/en-us/library/azure/dn578292.aspx</a>&nbsp;</p>
  122. <h3>Office 365 tenant administration APIs</h3>
  123. <p><strong>Purpose:</strong> To administer an Office 365 tenant that has been set up. For example to set a mailbox quota.<br /><br />Documentation: <a href="https://dev.office.com">https://dev.office.com</a> &nbsp;</p>
  124. <h3>Partner Center</h3>
  125. <p>Partner Center - <a href="https://partnercenter.microsoft.com">https://partnercenter.microsoft.com</a></p>
  126. <h3>Network Monitoring</h3>
  127. <p>Microsoft Message Analyzer <a href="https://technet.microsoft.com/en-us/library/jj649776.aspx">https</a><a href="https://technet.microsoft.com/en-us/library/jj649776.aspx">://technet.microsoft.com/en-us/library/jj649776.aspx</a>&nbsp;</p>
  128. <p>Telerik Fiddler <a href="https://www.telerik.com/fiddler">http</a><a href="https://www.telerik.com/fiddler">://www.telerik.com/fiddler</a></p>
  129. <p>POSTMAN <a href="https://www.getpostman.com/">https</a><a href="https://www.getpostman.com/">://www.getpostman.com</a><br /><br />&nbsp;</p>
  130. </div>]]></content:encoded>
  131.    </item>
  132.    <item>
  133.      <title>Microsoft Cloud Solution Provider program APIs - Onboarding Tutorial</title>
  134.      <link>https://docs.microsoft.com/archive/blogs/pandrew/microsoft-cloud-solution-provider-program-apis-onboarding-tutorial</link>
  135.      <pubDate>Wed, 12 Aug 2015 09:49:15 GMT</pubDate>
  136.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  137.      <guid
  138.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2015/08/12/microsoft-cloud-solution-provider-program-apis-onboarding-tutorial/</guid>
  139.      <description><![CDATA[I recently started working on the Microsoft CSP program looking at the APIs that partners use. I've...]]></description>
  140.      <content:encoded><![CDATA[<p>I recently started working on the Microsoft CSP program looking at the APIs that partners use. I've created a <a href="https://youtu.be/8RRssasC2Ys">walk through video of how you go about onboarding to these APIs.</a></p>
  141. <p>The video starts out walking through the Partner Center and showing the steps required to create an Integration Sandbox and to get the App ID's for use within your code. Next I start working with the Integration Sandbox and I show how to access the directory from an existing Azure subscription. Using that Azure subscription I add permissions for the App ID to access the directory through the Graph API. Lastly I show where to plug in the App ID and other required details into the C# sample code that we <a href="https://github.com/PartnerCenterSamples/Commerce-API-DotNet/">published on GitHub</a> and I run the sample code.</p>
  142. <p>This walk through was done with Windows 10, Internet Explorer 11 and Visual Studio 2015.</p>
  143. <p>I have a few more of these howto videos planned for working with the CSP APIs. Let me know if you have a suggestion for something to demo.</p>
  144. <p>&nbsp;</p>
  145. <p>Paul</p>]]></content:encoded>
  146.    </item>
  147.    <item>
  148.      <title>Office 365 URLs and IP Address Ranges Email Change Notification</title>
  149.      <link>https://docs.microsoft.com/archive/blogs/pandrew/office-365-urls-and-ip-address-ranges-email-change-notification</link>
  150.      <pubDate>Wed, 09 Jul 2014 17:05:00 GMT</pubDate>
  151.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  152.      <guid
  153.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2014/07/09/office-365-urls-and-ip-address-ranges-email-change-notification/</guid>
  154.      <description><![CDATA[For Office 365 customers who have restrictive firewalls for their employees it is important to have...]]></description>
  155.      <content:encoded><![CDATA[<p>For Office 365 customers who have restrictive firewalls for their employees it is important to have the right URLs or IP Addresses configured for uninterrupted access to Office 365. We have published this information on the TechNet page <a href="https://technet.microsoft.com/en-us/library/hh373144.aspx">Office 365 URLs and IP address ranges</a>. We have an RSS feed so that you can stay up to date with changes to this page. Some third-party companies provide applications that enable you to get email notifications of these changes. For example, one such third-party company is IFTTT Inc., and there is already an <a href="https://ifttt.com/recipes/188282-email-office-365-url-ip-changes">IFTTT recipe to do that</a> (IFTTT account required). Here&rsquo;s what an email from that might look like.</p>
  156. <p>&nbsp;</p>
  157. <p><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/7506.IFTTT-recipe-for-ip-address.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/7506.IFTTT_2D00_recipe_2D00_for_2D00_ip_2D00_address.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/7506.IFTTT-recipe-for-ip-address.png" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42/7506.IFTTT_2D00_recipe_2D00_for_2D00_ip_2D00_address.png" alt="" border="0" /></a></p>]]></content:encoded>
  158.    </item>
  159.    <item>
  160.      <title>Office 365 directory synchronization and avoiding accidental deletes</title>
  161.      <link>https://docs.microsoft.com/archive/blogs/pandrew/office-365-directory-synchronization-and-avoiding-accidental-deletes</link>
  162.      <pubDate>Fri, 30 May 2014 13:11:00 GMT</pubDate>
  163.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  164.      <guid
  165.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2014/05/30/office-365-directory-synchronization-and-avoiding-accidental-deletes/</guid>
  166.      <description><![CDATA[We have a new option those who use DirSync for directory synchronization with Office 365. It...]]></description>
  167.      <content:encoded><![CDATA[<p>We have a new option those who use DirSync for directory synchronization with Office 365. It monitors the staged delete updates&nbsp;that are to be sent to Azure AD and if they exceed a limit that you&nbsp;define then the delete operations are held until&nbsp;you review. This can&nbsp;help you to avoid accidental mass deletion of accounts from Azure AD. Details of how to set this up are here: <a href="https://social.technet.microsoft.com/wiki/contents/articles/24544.how-to-avoid-syncing-accidental-deletes-to-the-cloud-directory.aspx">https://social.technet.microsoft.com/wiki/contents/articles/24544.how-to-avoid-syncing-accidental-deletes-to-the-cloud-directory.aspx</a>&nbsp;</p>
  168. <p>This requires version 6765.0006 of DirSync. Version history is listed here: <a href="https://social.technet.microsoft.com/wiki/contents/articles/18429.microsoft-azure-active-directory-sync-tool-version-release-history.aspx">https://social.technet.microsoft.com/wiki/contents/articles/18429.microsoft-azure-active-directory-sync-tool-version-release-history.aspx</a></p>
  169. <p>[edited]</p>]]></content:encoded>
  170.    </item>
  171.    <item>
  172.      <title>TechEd USA Talks on Office 365 Identity Management</title>
  173.      <link>https://docs.microsoft.com/archive/blogs/pandrew/teched-usa-talks-on-office-365-identity-management</link>
  174.      <pubDate>Sun, 18 May 2014 18:10:51 GMT</pubDate>
  175.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  176.      <guid
  177.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2014/05/18/teched-usa-talks-on-office-365-identity-management/</guid>
  178.      <description><![CDATA[The PowerPoint slides and recordings for TechEd US are all published now. Below are links to the...]]></description>
  179.      <content:encoded><![CDATA[<p>The PowerPoint slides and recordings for TechEd US are all published now. Below are links to the Office 365 Identity Management talks that I presented and some related articles that have been published recently for more information. You can keep in touch with updates to Identity Management topics on Office 365 with this tag on the Office blogs.</p>
  180. <p><a href="https://blogs.office.com/featured_topics/identity/">https://blogs.office.com/featured_topics/identity/</a></p>
  181. <p><strong></strong>&nbsp;</p>
  182. <p><strong>TechEd US: Introduction to Microsoft Office 365 Identity&nbsp;Management</strong></p>
  183. <p>User management is easy in Office 365, if you just add all your users in the Office 365 admin portal&mdash;which works great for teams of less than 25 users. Larger organizations will want to use their existing user directory, and that integration can seem daunting. It doesn&rsquo;t have to be, and this session provides concepts and example scenarios that make identity management in Office 365 seem easy. We discuss user synchronization and why it is important, and talk about sign-in federation and when you would want to do that. We explain a simple Active Directory Federation Services deployment for you and talk about the interoperability program that Microsoft has called Works with Office 365 &ndash; Identity.</p>
  184. <p><a href="https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/OFC-B222">https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/OFC-B222</a></p>
  185. <p>&nbsp;</p>
  186. <p><strong>Office Blogs: Choosing a sign-in model for Office 365</strong></p>
  187. <p>This article is an introduction to the three models for identity management in Office 365 and it provides guidance for choosing which one is right for any customer scenario.</p>
  188. <p><a href="https://blogs.office.com/2014/05/13/choosing-a-sign-in-model-for-office-365/">https://blogs.office.com/2014/05/13/choosing-a-sign-in-model-for-office-365/</a></p>
  189. <p>&nbsp;</p>
  190. <p><strong>Office Blogs: Synchronizing your directory with Office 365 is easy</strong></p>
  191. <p>This article is a primer for setting up directory synchronization for Office 365.</p>
  192. <p><a href="https://blogs.office.com/2014/04/15/synchronizing-your-directory-with-office-365-is-easy/">https://blogs.office.com/2014/04/15/synchronizing-your-directory-with-office-365-is-easy/</a></p>
  193. <p>&nbsp;</p>
  194. <p><strong>TechEd US: Multi-Factor Authentication for Microsoft Office&nbsp;365</strong></p>
  195. <p>Multi-Factor Authentication is where a user is required to provide an account password and another form of authentication to sign-in. Office 365 now includes support for Multi-Factor Authentication where the second factor for authentication is a Cell Phone. This session describes how Office 365 customers can take advantage of Multi-Factor Authentication. It covers configuration, enrollment, and usage by users who are enabled for Multi-Factor Authentication. Best practices are included for Administrative accounts and for Office 365 assigned users, in addition to details of sign-in for Office 365 web-based applications and Office rich client applications.</p>
  196. <p><a href="https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/OFC-B250">https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/OFC-B250</a></p>
  197. <p>&nbsp;</p>
  198. <p><strong>Office Blogs: Announcement of Multi-Factor Authentication for Office 365</strong></p>
  199. <p>This article describes multi-factor authentication for Office 365 including its capabilities, availability and some future enhancements coming.</p>
  200. <p><a href="https://blogs.office.com/2014/02/10/multi-factor-authentication-for-office-365/">https://blogs.office.com/2014/02/10/multi-factor-authentication-for-office-365/</a></p>
  201. <p>&nbsp;</p>
  202. <p><strong>TechEd US: Microsoft Office 365 Directory Synchronization and Federation&nbsp;Options</strong></p>
  203. <p>You know by now that Office 365 uses Azure Active Directory and that you can synchronize accounts from your On-Premises Active Directory using the DirSync tool and you can do federated authentication using Active Directory Federation Services. This session answers many common questions about directory integration with Office 365. We also talk about three new key technologies that allow you to synchronize with non-Microsoft directories, to federate with non-Microsoft directories, and to do all of this with authentication from Office desktop client applications.</p>
  204. <p><a href="https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/OFC-B317">https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/OFC-B317</a></p>]]></content:encoded>
  205.    </item>
  206.    <item>
  207.      <title>Office 365 Switch Plans is okay now with a Custom Domain</title>
  208.      <link>https://docs.microsoft.com/archive/blogs/pandrew/office-365-switch-plans-is-okay-now-with-a-custom-domain</link>
  209.      <pubDate>Tue, 04 Mar 2014 17:26:41 GMT</pubDate>
  210.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  211.      <guid
  212.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2014/03/04/office-365-switch-plans-is-okay-now-with-a-custom-domain/</guid>
  213.      <description><![CDATA[Recently Office 365 added a new tool to allow customers to switch plans in the middle of a...]]></description>
  214.      <content:encoded><![CDATA[<p>Recently Office 365 added a new tool to allow customers to switch plans in the middle of a subscription period. I wrote about this <a href="https://blogs.office.com/2013/12/19/you-can-now-switch-plans-to-a-different-office-365-service-family/">here</a>. We had an issue with switching a plan if you were using a custom domain and we've corrected that now. You can Switch Plans even if you have a custom domain. Read the online help for Switch Plans <a href="https://office.microsoft.com/en-us/office365-suite-help/can-i-switch-to-a-different-office-365-plan-or-subscription-HA104031833.aspx">here</a>.</p>
  215. <p>While we had this issue you could still Switch Plans if you were willing to remove your custom domain from your Office 365 subscription and re-add it back after changing the subscription. Now you can just upgrade without the hassle.</p>]]></content:encoded>
  216.    </item>
  217.    <item>
  218.      <title>New Identity Federation Debug Tools for Office 365</title>
  219.      <link>https://docs.microsoft.com/archive/blogs/pandrew/new-identity-federation-debug-tools-for-office-365</link>
  220.      <pubDate>Thu, 05 Sep 2013 21:19:00 GMT</pubDate>
  221.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  222.      <guid
  223.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2013/09/05/new-identity-federation-debug-tools-for-office-365/</guid>
  224.      <description><![CDATA[The Microsoft Connectivity Analyzer tool was updated today. It now includes tooling for testing an...]]></description>
  225.      <content:encoded><![CDATA[<p>The Microsoft Connectivity Analyzer tool was updated today. It now includes tooling for testing an Office 365 federated identity provider. This can be used with an Office 365 tenant which is configured for federation with either ADFS or another WS-* based Security Token Service. It can help you to debug issues you have with the federated identity provider with simple tests. The tool is available for download from Microsoft at <a href="https://testconnectivity.microsoft.com/?tabid=Client">https://testconnectivity.microsoft.com/?tabid=Client</a>. Once downloaded and run you enter your Office 365 credentials and begin the login test of your federation configuration.</p>
  226. <p><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/metablogapi/4382.090613_0837_NewIdentity1.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42-metablogapi/4382.090613_5F00_0837_5F00_NewIdentity1.png" alt="" /></p>
  227. <p>Tests are done from the PC that you download the testing tool to. It will attempt to log in to Office 365 using the federation configuration. The testing will proceed and then show results which should help you to debug federation issues that you may be having.</p>
  228. <p><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/metablogapi/7345.090613_0837_NewIdentity2.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42-metablogapi/7345.090613_5F00_0837_5F00_NewIdentity2.png" alt="" /></p>
  229. <p>Here's the result showing that there were errors. You can review the detail to see what the issue is.</p>
  230. <p><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/28/42/metablogapi/7416.090613_0837_NewIdentity3.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-28-42-metablogapi/7416.090613_5F00_0837_5F00_NewIdentity3.png" alt="" /></p>
  231. <p>The tool is in beta now, so please provide feedback.</p>]]></content:encoded>
  232.    </item>
  233.    <item>
  234.      <title>Office 365 Directory Sync Quota Automated Increase to 300,000 Users</title>
  235.      <link>https://docs.microsoft.com/archive/blogs/pandrew/office-365-directory-sync-quota-automated-increase-to-300000-users</link>
  236.      <pubDate>Sun, 04 Aug 2013 17:22:37 GMT</pubDate>
  237.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  238.      <guid
  239.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2013/08/04/office-365-directory-sync-quota-automated-increase-to-300000-users/</guid>
  240.      <description><![CDATA[From https://community.office365.com/en-us/wikis/office_365_service_updates/974.aspx#jul2013
  241. New...]]></description>
  242.      <content:encoded><![CDATA[<p>From <a href="https://community.office365.com/en-us/wikis/office_365_service_updates/974.aspx#jul2013">https://community.office365.com/en-us/wikis/office_365_service_updates/974.aspx#jul2013</a></p>
  243. <p>New Office 365 tenants are limited to synchronizing 50,000 users from an on-premises Active Directory to the cloud. If a customer has more than 50,000 users and uses the DirSync tool to synchronize those to Office 365, they would previously need to call Office 365 Technical Support to get an increase in the quota. Without the quota increase customers will see errors from the DirSync tool when they exceed the quota. We recently released an improvement to the directory quota increase mechanism. This will increase a customer&rsquo;s directory quota to 300,000 objects automatically when they verify their first custom Internet domain. Customers that have more than 300,000 objects, or that do not verify any custom domains, will still need to call Office 365 Technical Support to increase their quotas. Existing customers who previously verified a custom domain may still see a quota limit of 50,000. Those customers should call Office 365 Technical Support to request a quota increase. We expect that as a result of this change, most customers will not need to call Technical Support for quota increases. For more information please read the details of the directory synchronization tool and the user object quotas on <a href="https://technet.microsoft.com/en-us/library/jj151831.aspx">TechNet</a>.</p>]]></content:encoded>
  244.    </item>
  245.    <item>
  246.      <title>TechEd 2013 Office 365 Identity and Security talks</title>
  247.      <link>https://docs.microsoft.com/archive/blogs/pandrew/teched-2013-office-365-identity-and-security-talks</link>
  248.      <pubDate>Fri, 07 Jun 2013 15:14:00 GMT</pubDate>
  249.      <dc:creator><![CDATA[Paul Andrew]]></dc:creator>
  250.      <guid
  251.        isPermaLink="false">https://blogs.msdn.microsoft.com/pandrew/2013/06/07/teched-2013-office-365-identity-and-security-talks/</guid>
  252.      <description><![CDATA[I'm just back from TechEd in New Orleans. You can view my talk on Office 365 Identity...]]></description>
  253.      <content:encoded><![CDATA[<p>I'm just back from TechEd in New Orleans. You can view my talk on Office 365 Identity here.</p>
  254. <p><a href="https://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/ouc-b211">https://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/ouc-b211</a></p>
  255. <p>&nbsp;</p>
  256. <p>And here's my talk on Office 365 Security that I presented with Andy O'Donald.</p>
  257. <p><a href="https://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/ouc-b205">https://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/ouc-b205</a>&nbsp;</p>]]></content:encoded>
  258.    </item>
  259.  </channel>
  260. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//blogs.msdn.microsoft.com/pandrew/feed/

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda