SCA Configuration - SecContacts.CustomDatasourceNames
SecContacts.CustomDatasourceNames
This setting allows administrators to customize the IDs and display names of datasources shown in SCA. This is useful when datasource names should match internal terminology or when multiple instances of the same datasource type are configured.
Secure Contacts App has a default id and name for any datasource which is available in the App. e.g. AAD - AzureActiveDirectory
default datasource id's currently available:
AAD, APC, GAL, D365, DVRS, ABS, SMC
With this setting you can change id and name of any datasource which is presented to the user.
Name:
SecContacts.CustomDatasourceNamesValue:
[{"defaultid":"<default id>", "customid":"<custom id>", "customname":"<custom name>"}]
The Value property is a JSON Array of defaultid customid customname trio.
You can add one or multiple custom datasource names here.
Replace <default id> with the default datasource id you want to change
e.g.
AAD
Replace <custom id> with your custom datasource id
e.g.
CORP
Replace <custom name> with your custom datasource name
e.g.
Corporate Directory
Configuration fields
defaultid
string
Yes
The original datasource ID assigned by SCA.
customid
string
Yes
Custom datasource ID used internally by SCA. Must not contain whitespace characters.
customname
string
Yes
Display name shown to users in the SCA interface.
Examples
Rename a single datasource
Result: AAD → CORP AzureActiveDirectory → Corporate Directory
Rename multiple datasources
Result: AAD → CORP AzureActiveDirectory → Corporate Directory
SMC → MKT SharedMailboxContacts → Marketing Contacts
ABS → SUP AzureBlobStorage → Support Directory
Rename multiple datasources of the same type
When multiple datasources of the same type are configured, SCA automatically assigns sequential IDs. Example: AAD1, AAD2 or ABS1, ABS2 etc.
These dynamically assigned IDs can also be customized using this setting.
Result: AAD1 → CORP AzureActiveDirectory1 → Sales Directory
AAD2 → MKT AzureActiveDirectory2 → Marketing Contacts
A resync as discribed here is mandatory after you have applied changes to SecContacts.CustomDatasourceNames.
Last updated
Was this helpful?