This is expected behavior if you are using forMSGraphAccess: true
with the side-loaded add-in.
You can set forMSGraphAccess: false
and call the getaccesstoken()
and you will no longer see the 13012 error
.
Otherwise you need to deploy the add-in via the admin center if you are using forMSGraphAccess: true
If you still run into any issues, I would recommend reaching out on the Office forums for assistance.
https://github.com/OfficeDev/office-js/issues/2711
If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar information.