Share
ReportHi,
I am working on introducing a customer portal for a local council who currently have
- Dynamics CRM 2013 (on-premise and supported in-house) mastering external customers and case data
- Forms (third party solution - firmstep)
- CMS (third party solution - zengenti)
- Bi-directional Integration service (in-house developed Web API)
There are also plans to introduce Azure (logic apps, service bus and azure B2C for identity management)
In an ideal world i would love to consider ADXstudio but assume not an option as a retired product.
That points me towards Microsoft Portals, but this requires an upgrade to Dynamics 365
The timescales for the Dynamics upgrade is end of 2017 (that may be 2016 in-premise or 365) and i need a Portal in by September 2017
I then thought about spinning up a Dynamics 365 instance (purely for the Portal) in the cloud and use a data synchronisation tool (SSIS with Kingsway add-on or Scribe for example) and running until such time we have upgrade, but this is costly sand complex
My current thinking is to look to implement Azure B2C for sign-up, sign-in, profile management & password resets, utilising our in-house integration service (integration to and from Dynamics) and Dynamics 2013 to house the customer data.
My questions really are
1) any other options i maybe should consider re, Portal
2) data synchronisation option (2013 on-prem to Dynamics 365)
3) Azure B2C - is this a viable option, do i need to migrate the integration service into a DMZ (currently internal) or migrate as an Azure API app?
4) Azure B2C - would prefer the email address/password approach - can we invite our existing customer base (who have a primary email address stored on the contact record) to register?
4) Azure B2C - at some point when we upgrade our Dynamics CRM what happens to the usernames and passwords? can i easily migrate them - does the end-user have to re-register or simply reset password or do nothing!
Thanks in advance
Richard
*This post is locked for comments
All responses (
Answers (
1,947
