title: Installing npm private package gives back 404/405 - "is not in the npm registry"
body: <pre><code>npm ERR! code E404
  npm ERR! 404 Not Found - GET http://registry.npmjs.org/@office%2fintegration-sdk - Not found
  npm ERR! 404 
  npm ERR! 404  '@office/integration-sdk@*' is not in the npm registry.
  npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
  npm ERR! 404 
  npm ERR! 404 Note that you can also install from a
  npm ERR! 404 tarball, folder, http url, or git url.
  </code></pre>
  <p>We have <strong>private bitbucket repo</strong>, with package code, that we want to <strong>make npm private package</strong> out of it.
  I've managed to publish it thru CLI with <code>npm publish</code>, and with the bitbucket pipeline.
  And it can be installed fine, as long as i am logged in with <code>npm login</code>.
  But we want to be able to install it without logging to npm(when deployed etc..), and i thought NPM_TOKEN is there for those reasons.</p>
  <p>I've tried buncha stuff in .npmrc file, mostly like:</p>
  <pre><code>@office:registry=https://registry.npmjs.org/:_authToken=&lt;'read/publish token from npm'&gt;
  </code></pre>
  <p>Steps:</p>
  <ul>
  <li>npm publish</li>
  <li>check npm - package looks good, updated, etc..</li>
  <li>run install command - npm i @office/integration-sdk</li>
  <li>Fails with either 404(most of the time), and with 405 Method not Allowed when i have  <em>@office:registry=https://registry.npmjs.org/@office</em>.</li>
  </ul>
  <p>One thing that might be causing this.. We only have user account on npm i guess, it is Pro account with private packages thing. But we didn't create organization. Could that be a problem, i mean it can be published, and installed when logged in, and also public packages can be installed just fine when not logged in.</p>