The ability to create contacts requires each individual user to go through the CRM OAuth flow, in order to respect all existing CRM settings and only create contact records that they would be able to directly in CRM. When a user clicks on the Add to CRM button, Sales Navigator will make a call to determine their CRM connection status, and display a prompt to sign into CRM if not already authenticated. The user will also be restricted to signing into the same CRM instance that is already connected to CRM Sync and will receive an error message otherwise.

*If Email and/or Phone have already been entered directly into CRM or Sales Navigator, they will be pre-populated.

Yes, each individual user is limited to creating 1,000 leads AND contacts per month from Sales Navigator and will receive an error message if they try to exceed this limit.

The API limits for Dynamics 365 can be found here.  For the Team Member license, there is a daily limit of 5,000 API calls per person. The Lead Creation feature is limited to 1,000 leads or contacts per user per month, thus well below the API limits. If the limit is hit, users will receive an error message.

No, the Lead Creation functionality supports a predetermined set of standard contact fields which cannot be customized.

Yes, this is supported.

• The CRM end-user must be allowed to authenticate via OAuth, have API access enabled for the Dynamics org/level and read and write access to the standard lead fields and the lead record, and no custom validation rules for the lead record on unsupported fields. 
• Note that OAuth will fail if the Dynamics Admin has blocked the Sales Navigator Dynamics App.

No, form level permissions / validations in Dynamics will not be enforced as all interaction occurs via Dynamics Web API.   This includes individual fields that are marked as required, custom business rules, and duplicate detection rules.  This is a documented behavior of Dynamics 365 Web API.

No

Lead Creation runs on behalf of each individual CRM user who must go through their own OAuth process. As such, users can't perform any action/write back any information they cannot do within Dynamics 365, and user activity is subject to whatever level of auditing comes with the user’s Dynamics 365 system.

The Lead Creation feature requires end-users to be signed into the same Dynamics 365 instance that is connected to CRM sync. To check what instance they are signed into, and sign out/sign in again, users should navigate to Settings and scroll down to the CRM Settings section at the bottom.

Yes, SSO is supported, provided that the user has previously signed into Dynamics 365.

Matching refers to matching a Sales Navigator Lead profile to a Dynamics 365 Lead or Contact record. Sales Navigator will inform users when:

1. The Lead profile is already matched to a Dynamics 365 Contact or Lead record and
2. There are existing records that might be a match for the Lead profile based on First Name and Last Name.

Note that performing a match will NOT update any information on the Dynamics 365 record, and the event will not be logged in Dynamics 365 as there is no change.

Because Lead Creation supports all standard fields out-of-the-box, customers who have many customized fields may not be able to use Lead Creation.

No, it’s not required that a Lead is associated with an opportunity.