title: GET filesFolder API issue
body: <p>We have a new problem when run this request: <a href="https://docs.microsoft.com/en-us/graph/api/channel-get-filesfolder?view=graph-rest-1.0&amp;tabs=http" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/graph/api/channel-get-filesfolder?view=graph-rest-1.0&amp;tabs=http</a></p>
  <p>That is, <strong>GET /teams/{id}/channels/{id}/filesFolder</strong></p>
  <p>Previously, if a Team Channel was created via the API, it wasn't linked to a folder with files, until a user clicks Files in a Teams client and thus initializes it. And until it was initialized, the request would return <strong>Not Found 404</strong>.</p>
  <p>However, since around February 25, 2021, in case the authenication uses MFA, we now get this error: <strong>Value cannot be null. Parameter name: token</strong>. But, the Authorization Token <strong>is</strong> present in the request as we verified with a traffic capture. Once you initialize the folder by clicking Files, the request starts to return valid data.</p>
  <p>Is this a bug? Thanks.</p>
  <pre><code>GET https://graph.microsoft.com/v1.0/teams/.../channels/.../filesFolder?$select=id,name,webUrl,parentReference HTTP/1.1
  Content-Type: application/json
  User-Agent: &lt;...&gt;
  Authorization: Bearer ...
  Host: graph.microsoft.com
  Connection: Keep-Alive
  
  HTTP/1.1 400 Bad Request
  Cache-Control: private
  Content-Type: application/json
  request-id: ...
  client-request-id: ...
  x-ms-ags-diagnostic: {&quot;ServerInfo&quot;:{&quot;DataCenter&quot;:&quot;West Europe&quot;,&quot;Slice&quot;:&quot;SliceC&quot;,&quot;Ring&quot;:&quot;5&quot;,&quot;ScaleUnit&quot;:&quot;005&quot;,&quot;RoleInstance&quot;:&quot;AGSFE_IN_67&quot;}}
  Strict-Transport-Security: max-age=31536000
  Date: Mon, 01 Mar 2021 19:38:40 GMT
  Content-Length: 310
  
  {
    &quot;error&quot;: {
      &quot;code&quot;: &quot;BadRequest&quot;,
      &quot;message&quot;: &quot;Value cannot be null.\r\nParameter name: token&quot;,
      &quot;innerError&quot;: {
        &quot;date&quot;: &quot;2021-03-01T19:38:41&quot;,
        &quot;request-id&quot;: &quot;...&quot;,
        &quot;client-request-id&quot;: &quot;...&quot;
      }
    }
  }
  </code></pre>