1 Answer
- Newest
- Most votes
- Most comments
0
It was a user that was not populating correctly from AD, deleted user and added, all was then correct and the charge stopped happening
answered 6 years ago
Relevant content
- asked 2 years ago
- asked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
