Hi Sevil,

At the moment, alarm ownership can only be taken by a user, it cannot be assigned to another user, not directly, not through automation. As a result, it is not possible for an Automation Script triggered by a Correlation Rule to copy the owner of one alarm to another.

There are a couple of related alternatives, although neither fully addresses your use case probably:

• A Correlation Rule can acknowledge an alarm, but in that case the owner becomes the Correlation Rule itself rather than the user who owns the original alarm.
• If the original owner is currently online, you could attempt to attach that user to the script using engine.FindInteractiveClient(). In that scenario, the script continues to run in the context of the attached user, which may allow the user to effectively confirm a Take Ownership action suggested by the correlation.