@ncw thanks for getting back to me.
Yeah I tried options 3 and 4 (other) as suggested and no luck.
My config is:
type = webdav
url = https://[company].sharepoint.com/personal/[suer]/Documents
vendor = other
Running:
rclone ls share: -vv --dump requests
This is the dump I get:
2020/03/05 13:52:00 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2020/03/05 13:52:00 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2020/03/05 13:52:00 DEBUG : HTTP RESPONSE (req 0xc000143200)
2020/03/05 13:52:00 DEBUG : HTTP/2.0 403 Forbidden
Content-Length: 13
Content-Type: text/plain; charset=utf-8
Date: Thu, 05 Mar 2020 13:52:00 GMT
Microsoftsharepointteamservices: 16.0.0.19819
Ms-Cv: nzvSR8FQALCdGiRj0m1mwA.0
P3p: CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"
Request-Id: 47d23b9f-50c1-b000-9d1a-2463d26d66c0
Sprequestguid: 47d23b9f-50c1-b000-9d1a-2463d26d66c0
X-Content-Type-Options: nosniff
X-Forms_based_auth_required: https://x.sharepoint.com/_forms/default.aspx?ReturnUrl=/_layouts/15/error.aspx&Source=/personal/x
X-Forms_based_auth_return_url: https://x.sharepoint.com/_layouts/15/error.aspx
X-Idcrl_auth_params_v1: IDCRL Type="BPOSIDCRL", EndPoint="/personal/x/_vti_bin/idcrl.svc/", RootDomain="sharepoint.com", Policy="MBI"
X-Ms-Invokeapp: 1; RequireReadOnly
X-Msdavext_error: 917656; Access+denied.+Before+opening+files+in+this+location%2c+you+must+first+browse+to+the+web+site+and+select+the+option+to+login+automatically.
X-Msedge-Ref: Ref A: 1F237D9895F443C49D66B81BDC12DE2B Ref B: DB3EDGE1621 Ref C: 2020-03-05T13:52:00Z
X-Powered-By: ASP.NET
X-Sharepointhealthscore: 2
2020/03/05 13:52:00 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2020/03/05 13:52:00 ERROR : : error listing: couldn't list files: 403 FORBIDDEN: 403 Forbidden
2020/03/05 13:52:00 Failed to ls with 2 errors: last error was: couldn't list files: 403 FORBIDDEN: 403 Forbidden
This is why I then looked into Chrome to see this redirect happens automatically in the browser which generates a auth token cookie it seems.