Darren Kattan- I'm confused by your question. The policy setting is "silently configure OneDrive using primary Windows account", so by definition it uses whatever Windows credentials (presumably a work/domain account) the user signed into their PC with and passes them to AAD. In order to configure the OneDrive client silently the user would necessarily have to *have* a OneDrive in the cloud, so the credentials used to sign into a PC and to OneDrive would, thus, have to be the same... It doesn't provision a OneDrive for a user from scratch, it just passes their credentials through to AAD so they don't have to manually sign into the OneDrive client after they just logged into the PC. I may be misunderstanding what you're asking, but generally my experience has been:
1. User signs into a computer using a domain account for the first time (or the first time after OneDrive and Group Policy have been setup)
2. After a minute or so the Explorer process restarts and maps the OneDrive folder, popping up a message explaining that the OneDrive client is being configured.
3. On subsequent logins the OneDrive is just there as usual, no muss, no fuss.
That being said, I did notice that sometimes directly after imaging a computer the first user to sign in might not trigger the OneDrive silent configuration process - whether that's because my Group Policy settings haven't fully been applied or what I'm not sure, but a reboot always sees the OneDrive client configure itself on the user's next login.
Hope this helps!
--R