I'm wondering if anyone else saw some new user records created by Microsoft (presumably) on July 4th. The following 4 user records appeared in our environment (production and sandboxes) on Saturday and are interfering with our integration. We are not able to edit or delete these records.Dynamics365Athena-CDStoAzuredatalakeDynamics365Athena2-CDStoAzuredatalakePowerqueryonline-CDStoAzuredatalakeDynamics365EnterpriseSales-CDStoAzuredatalakeI've opened a ticket with Microsoft and will update here when I have news.
Hi Jill~Yes - all 4 accounts were added to our Dev, Test, and Prod environments between July 4th and 5th. So, did Microsoft say that we are to have the accounts removed/deactivated or leave them as-is?Thanks for letting us know about this! You've saved many people from doing a lot of digging. It's much appreciated.
"We are yet to receive the updates from the product team on this issue. We are following with the product team on top priority. We will keep you posted once we hear the updates from them. Thank you!"Yesterday, we asked the following questions and received the following answers:
Q: Why has it been 5 days and your team is just asking questions about impact as opposed to removing or modifying the user in our environment?A: The issue description/details are need to fully engage the team for resolution and to expedite. Now that we have the full business impact available we have engaged the dev team to look into this matter with urgency. We will continue to provide you updates on the status as we learn more.Additionally, those new system users seems to be added for backend work that is related to new updates. The strange part is that it is impacting your integrations. Out engineering team would have tested those updates, but your integration scenario my be a special case
Our integration was designed to only look for real users based on the first and last name not being blank and another custom field not being blank. The addition of these 4 user records called out a deficiency in our logic in that the first names in these records are not blank - they are null - so that is what threw things off for us. The most frustrating part is that we still have no idea why we all got these user records created in our environments or what their purpose is.
Application users are created during system provisioning for setup and configuration management. Application users can also be used for performing back-end services.
Most of these users are hidden from user views but they can be found by using the Advanced Find on the Users entity. Do not delete or modify these users including changing or reassigning security role.
And we are sorry for not notifying you in advance. We have given this feedback to the product team and they were sorry for the inconvenience caused and agreed to send notifications to customers before any such releases."
If you've found this thread useful, dive deeper into User Group community content by role