Ominous vault made by /setblock or /fill not taking ominous key

I have did a search first make sure I did not do a duplicate ticket. I have placed a search result in a screenshot to show this.

I have did a search first make sure I did not do a duplicate ticket. I have placed a search result in a screenshot to show this.

Can confirm, relates to MC-270062.
Note that the command provided has a small issue, the first letter of "Ominous" should not be capitalized.

Invisible826 this is a report for bedrock edition not Java!

This bug is driving me insane.

I think Mojang needs to make it easier to get the ominous vault. If they could just add the item to the creative inventory it would make mapmaker's lives a whole lot easier. This bug is terrible.

For the builder looking to circumvent this limitation, I just attached a .mcstructure file. It contains the original vault data inside. So, If you create a behavior pack, then put this mcstructure on "structures" folder, you can use /structure load ominous_vault ~ ~ ~ to spawn a functional ominous vault, or use a structure block and load "ominous_vault"

For the builder looking to circumvent this limitation, I just attached a .mcstructure file. It contains the original vault data inside. So, If you create a behavior pack, then put this mcstructure on "structures" folder, you can use /structure load ominous_vault ~ ~ ~ to spawn a functional ominous vault, or use a structure block and load "ominous_vault"

It’s almost been two years at this point and this feature still hasn’t been fixed - could Mojang please fix this for mapmakers, and perhaps add this as a block in the creative inventory. Thanks.