@Marco Villasenor I found the diagnostic tool I was referring to. It is https://testconnectivity.microsoft.com/tests/o365This will allow you to verify if it is an Office 365 configuration or account issues versus an Acumatica issue.
We have a dedicated, licensed user in Office 365 for our Acumatica email address. I would definitely try to see if authorizing via a licensed user account resolves the issue (versus a shared mailbox). That should be a fairly simple test to run. Good luck!
We are running Acumatica version 21.119.0030. I never found an error log in Acumatica providing more detail on the issue. At one point, I had a link to an diagnostic tool within Office 365 that would verify your connection. Unfortunately, I haven’t been able to find that link to share it. When I ran that with basic auth, I got the same error as I got with Acumatica. I also got the same error when I tried to connect using basic auth via Windows Mail program. That is the point at which I knew this wasn’t specific to Acumatica. It was a general error related to basic auth and our Office 365 tenant. So I never spent a lot of time trying to find more detailed error logs in Acumatica. When I moved Acumatica to modern auth, it worked right away. But again, I was using the 2021 R2.
@jvaliente51 You could certainly try to see if OAuth works in Acumatica without setting up these API permissions. I included them because that was in the documentation I followed. I didn’t have to worry about IT approval since I am a global Admin in our Office 365 tenant so I have full permissions. I can’t say what permissions are required to be able to configure Microsoft Graph within Azure. Best of luck!
@jvaliente51 The instructions say to choose Microsoft Graph and then select application permissions. In reality, all of these are delegated permissions. So the instructions should read Select Azure Active Directory > App registrations, and then select your client application. Select API permissions > Add a permission > Microsoft Graph > Delegated permissions. If you then use the search box, you should see each of these. The final result of my permissions settings is below: I hope this helps!
I resolved this issue on Monday. I changed the authentication method from Basic Authentication to Azure Modern Authentication. Microsoft is dropping support for basic authentication for IMAP and POP. I believe this is why this stopped working for us.I followed these instructions and it worked immediately. Good luck! By using the System Email Accounts (SM204002) form, you can create an email account for MS Office 365 account. Acumatica ERP uses the Azure AD service for authentication. We recommend opening Microsoft Azure Portal in the next tab of your browser, you will need to perform some configuration steps there. Step 1: To Specify the General Settings of the AccountTo specify the general settings of the account, do the following:Open the System Email Accounts (SM204002) form. On the form toolbar, click Add New Record. In the Summary area of the form, do the following: In the Account Name box, type the name of the system email account. In the Email Addr
Has there been any resolution here? We are running into the same issue with Office 365 Exchange. Everything was working fine and then stopped about a month ago. We can send emails, but can’t receive. We get the same error messages.Any progress, updates or ideas would be greatly appreciated.Thanks!
Yes, a transaction date/date entered is exactly what I need…. and then I need to be able to run the report based on that date. Is it possible to add the date somehow?
I was not aware that at the time the import scenario was created, it also created a data provider. I was assuming that the GI itself was the data provider. That is why I was adding fields to the GI and they were not available in the import scenario. I had not updated the data provider to reflect the new fields. That is why when I re-created it from the start, they fields were there. It is because that generated a new data provider with the new fields. Thanks for all your help!
I created a new GI and the fields were all available in the import scenario. The only thing that was different was 1) I gave it a new name and 2) I chose all fields (rather than selecting specific fields). So do you think the system somehow has the original GI definition in some cache somewhere and is referencing that rather than the updated version? I can easily re-build the GI. But I am concerned that when I later need to add fields or conditions to the GI that the system won’t “see” those updates. I guess the best bet is to include all fields so I don’t have to make any edits to the GI. Thanks for your help!
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.