<?xml version="1.0" encoding="utf-8"?>
<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/"
  version="2.0">
  <channel>
    <title>Jason Ross</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/jasonross/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/jasonross/feed.xml</link>
    <description>SharePoint Online Dedicated Support</description>
    <lastBuildDate>Tue, 16 Apr 2019 06:09:28 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>SharePoint Online Management Shell &amp; Forcing Modern Authentication</title>
      <link>https://docs.microsoft.com/archive/blogs/jasonross/sharepoint-online-management-shell-forcing-modern-authentication</link>
      <pubDate>Wed, 04 Oct 2017 09:00:51 GMT</pubDate>
      <dc:creator><![CDATA[Jason A Ross]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/jasonross/?p=85</guid>
      <description><![CDATA[I recently worked with a customer that had a unique ADFS setup within their organization. The...]]></description>
      <content:encoded><![CDATA[I recently worked with a customer that had a unique ADFS setup within their organization. The organization had added an ADFS Claim rule to block legacy authentication requests if they did not originate from an expected IP address range. After doing so Connect-SPOService still worked however, when saving credentials to a variable using Get-Credential then passing to Connect-SPOService it would fail.

When using Connect-SPOService by itself, it will prompt for credentials and you are able to login successfully. The moment you assign your credentials to a variable using Get-Credential then pass that variable to Connect-SPOService you will receive an error message saying: <em>The partner returned a bad sign-in name or password error.</em>

Remember, not everyone will have this issue. This has to do with the unique ADFS setup that I talked about in the opening paragraph of this Blog post. You may ask, why don't I just authenticate using Connect-SPOService by itself without saving my credentials to a variable? The answer is that if I want to re-use these credentials later in my PowerShell script, I will be unable to do so without the script stopping until I enter my credentials again as they are not assigned to a variable.

Below are the steps that work:
<pre>Connect-SPOService -Url https://contoso-admin.sharepoint.com</pre>
Below are the steps that do not work:
<pre>$creds = Get-Credential
Connect-SPOService -Url https://contoso-admin.sharepoint.com -Credential $creds
Connect-SPOService : The partner returned a bad sign-in name or password error. For more information, see Federation
Error-handling Scenarios.
At line:1 char:1
+ Connect-SPOService -Url https://contoso-admin.sharepoint.com -Credenti ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : NotSpecified: (:) [Connect-SPOService], IdcrlException
 + FullyQualifiedErrorId : Microsoft.SharePoint.Client.IdcrlException,Microsoft.Online.SharePoint.PowerShell.Connec
 tSPOService</pre>
The workaround that we found was to add a registry key on the client computer that is using the SharePoint Online Management Shell. Once we add the registry key it forced Modern Authentication and we were able to get this scenario to work. Below is the registry key:
<pre>HKEY_CURRENT_USER\Software\Microsoft\SPO\CMDLETS]
"ForceOAuth"=dword:00000001</pre>
Now when we store our credentials in a variable and pass that variable to Connect-SPOService it works. Please keep in mind that this post was created in October of 2017 and may no longer be relevant in future releases in the SharePoint Online Management Shell. Also, always be careful when modifying the registry and take a backup before doing so.]]></content:encoded>
    </item>
    <item>
      <title>SharePoint Online and Mapped Network Drives</title>
      <link>https://docs.microsoft.com/archive/blogs/jasonross/sharepoint-online-and-mapped-network-drives</link>
      <pubDate>Tue, 08 Aug 2017 12:57:20 GMT</pubDate>
      <dc:creator><![CDATA[Jason A Ross]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/jasonross/?p=75</guid>
      <description><![CDATA[Mapped network drives are become a thing in the past with SharePoint Online as we now have the...]]></description>
      <content:encoded><![CDATA[Mapped network drives are become a thing in the past with SharePoint Online as we now have the <a href="https://support.office.com/en-us/article/Get-started-with-the-new-OneDrive-sync-client-in-Windows-615391c4-2bd3-4aae-a42a-858262e42a49">OneDrive for Business Sync Tool</a> that can be used to sync files from SharePoint Online or OneDrive for Business. The sync client offers a seamless way to sync files from your devices and it just works.

If you are still using mapped network drives you may run into issues if your client PC is not configured correctly. Also, with SharePoint Online you will have to make sure to login and authenticate to SharePoint Online using a web browser and select <strong>Keep me signed in</strong> during login to make sure the mapped network drive stays authenticated.

Below are things to remember when using mapped network drives with SharePoint Online/OneDrive for Business:
<ol>
 	<li>Make sure the WebClient service is set to start <strong>Automatically</strong> and not <strong>Manually</strong> in Service.msc (Start &gt; Run &gt; Services.msc)</li>
 	<li>Make sure that all of your SharePoint Online and OneDrive for Business URL's are in the <strong>Trusted Sites</strong> list in <strong>Internet Explorer</strong></li>
 	<li>Browse to your SharePoint site and login and make sure to click <strong>Keep me signed in</strong> during login which will create a persistent cookie</li>
 	<li>Attempt to map the network drive</li>
</ol>
If you reboot your PC you will need to make sure that:
<ol>
 	<li>You open a web browser and navigate to your SharePoint Online site</li>
 	<li>Make sure to click <strong>Keep me signed in</strong> check box to create a persistent cookie</li>
</ol>
&nbsp;

Additional information can be found <a href="https://support.microsoft.com/en-us/help/2616712/how-to-configure-and-to-troubleshoot-mapped-network-drives-that-connec">here</a> which is a Microsoft support article.]]></content:encoded>
    </item>
    <item>
      <title>How to Complete a Network Trace in Internet Explorer</title>
      <link>https://docs.microsoft.com/archive/blogs/jasonross/how-to-complete-a-network-trace-in-internet-explorer</link>
      <pubDate>Tue, 08 Aug 2017 06:53:31 GMT</pubDate>
      <dc:creator><![CDATA[Jason A Ross]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/jasonross/?p=55</guid>
      <description><![CDATA[Below are the steps to complete a network trace in Internet Explorer and save the trace file:...]]></description>
      <content:encoded><![CDATA[Below are the steps to complete a network trace in Internet Explorer and save the trace file:
<ol>
 	<li>Open <strong>Internet Explorer</strong></li>
 	<li>Press <strong>F12</strong> (Or click the Gear icon &gt; F12 Developer Tools)</li>
 	<li>Click the <strong>Network</strong> tab</li>
 	<li>Reproduce the issue by navigating to the website</li>
 	<li>Once done click the <strong>Save</strong> button</li>
 	<li>Give the trace a filename and click the <strong>Save</strong> button which will save it as a .har file or .xml file</li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>Find SharePoint Online Site Owner</title>
      <link>https://docs.microsoft.com/archive/blogs/jasonross/find-sharepoint-online-site-owner</link>
      <pubDate>Mon, 07 Aug 2017 13:13:36 GMT</pubDate>
      <dc:creator><![CDATA[Jason A Ross]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/jasonross/?p=45</guid>
      <description><![CDATA[If you need to find out who a site owner is in SharePoint Online you can do this leveraging the...]]></description>
      <content:encoded><![CDATA[If you need to find out who a site owner is in SharePoint Online you can do this leveraging the SharePoint Online Management Shell. You must first have the SharePoint Online Management Shell installed on your computer. You need to be a Global Administrator or have a role that allows you to have access to the Tenant Admin site to perform the below steps.
<ol>
 	<li>Download the SharePoint Online Management Shell from https://www.microsoft.com/en-us/download/details.aspx?id=35588</li>
 	<li>Install the SharePoint Management Shell by launching the MSI installation package</li>
 	<li>Once installed open the SharePoint Online Management Shell</li>
 	<li>Use Connect-SPOService to connect to your tenant admin site. Below is an example to find the site owner:</li>
</ol>
<pre>Connect-SPOService -Url https://contoso-<span>admin</span>.sharepoint.com -Credential jason@<span>contoso.onmicrosoft.com</span>

$site = Get-SPOSite -Identity https://<span>contoso</span>.sharepoint.com

$site | select Url,Owner

Url Owner
--- -----
https://contoso.sharepoint.com/ jason@<span>contoso.onmicrosoft.com</span></pre>
&nbsp;]]></content:encoded>
    </item>
  </channel>
</rss>