title: Paging in MS Graph API
body: <p><a href="https://graph.microsoft.io/en-us/docs/concepts/paging" rel="noreferrer">Graph API Paging</a> explains that the response would contain a field <code>@odata.nextLink</code> which would contain a <code>skiptoken</code> pointing to the next page of contents.</p>
  
  <p>When I test the API, I'm getting a fully-qualified MS Graph URL which contains the <code>skiptoken</code> as a query param. E.g. Below is the value I got for the field <code>@odata.nextLink</code> in the response JSON.
  <code>https://graph.microsoft.com/v1.0/users?$top=25&amp;$skiptoken=X%27445370740200001E3A757365723134406F33363561702E6F6E6D6963726F736F66742E636F6D29557365725F31363064343831382D343162382D343961372D383063642D653136636561303437343437001E3A7573657235407368616C696E692D746573742E31626F74322E696E666F29557365725F62666639356437612D333764632D343266652D386335632D373639616534303233396166B900000000000000000000%27</code></p>
  
  <p>Is it safe to assume we'll always get the full URL and not just the <code>skiptoken</code>? Because if it's true, it helps avoid parsing the <code>skiptoken</code> and then concatenating it to the existing URL to form the full URL ourselves.</p>
  
  <p><strong>EDIT</strong> - Compared to MS Graph API, response obtained from Azure AD Graph API differs in that the JSON field <code>@odata.nextLink</code> contains only the <code>skipToken</code> and not the fully-qualified URL.</p>