This article provides an overview of how to log into Affinity using Microsoft Exchange Credentials. The article also provides common troubleshooting steps you can take in the event you are unable to log in.
To use Affinity, you will not need to create a custom password. Affinity leverages your email address and password for login purposes.
There are currently two ways to log into Affinity using your exchange credentials, regardless of which option you choose you will need to know the following information before logging in:
- Microsoft email address
- Microsoft email password
- Username (if applicable)
- Microsoft Exchange URL (EWS URL)
Option #1: Logging in via your Custom organization URL (Recommended)
Logging into Affinity via your custom organization URL is simple and straightforward. With your credentials navigate to the Exchange login page on Affinity. Organization URLs are typically formatted as follows:
Option #2: Logging in via Affinity homepage
You may log into Affinity via the Affinity homepage at www.affinity.co. Affinity will default to a generic EWS URL for your convenience. Important to note, some organizations have a custom EWS URL. You may click "Advanced Settings" to change the URL if needed. (See your IT administrator if you unsure which URL to use)
- I am suddenly logged out of Affinity and I can no longer log in?
- Trying to log in for the first time, using the correct/updated passwords and email login - but I still can't get in?
- We recently changed email servers and now I can't see any of my email interactions in Affinity?
- My company uses Single-Sign On, and it's not working with Affinity.
1) I am suddenly logged out of Affinity and I can no longer log in?
Since Affinity uses your email credentials to login, once you change your email password, it will cause Affinity to log you out and stop emails from syncing. To remedy this, simply log back in using your updated credentials on your custom organization URL:
If you are still unable to log into Affinity, check to see if your password is still valid. The simplest method to verify this would be to log out of your Microsoft Exchange account then log back in by manually typing in the password or an incognito browser (avoid using any saved passwords/password managers).
If you cannot remember your password, simply do a "password reset" through Microsoft Exchange, and then try again.
If you are still having problems logging in, please contact support: firstname.lastname@example.org.
2) Trying to log in for the first time, using the correct/updated passwords and email login - but I still can't get in?
There may be two reasons for this. In some cases, you may have an Alias (username) that you may be unaware of. (If you are unsure of any Alias, please confirm with your IT team.)
That Alias (username) should be entered in the following location:
The other potential reason for not being able to login, is having a completely different login email address for internal use.
If you are unsure, please double-check with your IT team for more details.
Lastly, if you are hosting your own Exchange servers, the EWS URL will be different than the default (shown below):
You may need to contact your IT team to figure out what the correct EWS URL is.
Occasionally, your organization will host its own Exchange (Office365) server. In this case, your EWS URL will be a custom URL (example below):
You can also find/edit your current organization's EWS URL by going to your custom affinity URL, then selecting..:
Please check with your IT for the correct EWS URL, and contact email@example.com for further support.
This solution is a bit more involved, but if your organization is using SSO, and your identity provider supports OpenID Connect, or SAML 2, we can integrate this into our authentication process. Your IT team would then have to configure what's called an EWS Impersonation Account so we could sync data. You can see details to set this up here.
- If MFA is turned on for your organization you may have to look into app passwords for your team. See instructions on how to create an application specific password here.
- Make sure the EWS Url the user entering is correct. Instructions above.
- There may be a firewall in place that requires you to whitelist our IPs. Our production IPs are: 126.96.36.199 or 188.8.131.52
- Exchange authentication uses basic authentication (email/password), there may be settings preventing us from connecting this way. You can either turn this off or explore our SSO option if basic authentication does not work for your team.