Hi, We are deploying provisioning policy from Sandbox to Production for Windows Local Connector, Policy works as expected in Sandbox but not in Production and we are unable to create account in Production. We have below provisioning policy in Connector. { "name": "Account", "description"…

I believe you have Identity attribute hostname, check that mapping and transform if any. Looks like hostname attribute is empty for whatever user you are testing.

How do you get the hostname, somewhere it has to be defined rite.

So, as per document we have hostName in samAccount if Disable Qualifying Local Objects is unchecked, which is our case it is. [image] Moreover, we never defined in our sandbox, then how is it working?

Windows Local Connector Provisioning

Identity Security Cloud (ISC) ISC Discussion and Questions

ashishbhatia_custih (Ashish Bhatia) October 22, 2023, 2:39pm 3

Hi Krishna,

No, we don’t have any attribute like that. Moreover I deployed the same policy for multiple windows sources and it replaces the hostname at run time in Sandbox, but same didn’t work in Production.

Topic		Replies	Views
Unable to provision new accounts in AD ISC Discussion and Questions identity-security-cloud , provisioning	22	188	August 2, 2025
Webservice VA connector account creation ISC Discussion and Questions webservice-connector , apis , identity-security-cloud , provisioning	16	178	November 11, 2024
SAP Direct connector - provisioning policy attributes not populated ISC Discussion and Questions identity-security-cloud , provisioning	3	185	July 19, 2024
Web Service Connector - Create Account Error : Identity Attribute was not Found ISC Discussion and Questions webservice-connector , identity-security-cloud , provisioning , connectors	5	120	December 26, 2025
Native Identity Issue with Web Service Connector ISC Discussion and Questions webservice-connector , apis , identity-security-cloud , provisioning	14	768	November 30, 2024

Windows Local Connector Provisioning

Related topics