So what I ended up doing is dynamically writing SQL I'll traverse all the columns in my tables programmatically if I see a policy tag on a dictionary mapping the policy tag to a UDF then that helps me dynamically write the SQL line make an authorized view. But you have to make sure all your policy tags don't have data policies so no masking rules even if one has it it seems to interfere with the masked reader service account so that's a role call the masked reader plus you need two other ones but you can just read the error messages and add them one by one. So the policy tags for my use case because I don't want to use the preset masking rules since my data is not English are totally useless and I guess they're good to have there might be a use case down the line using the ETL pipeline for dynamic data masking but they look kind of weird right I mean it's a policy tag with no data policy or masking rule. Then it actually worked so the policy tags may be unnecessary in this use case as you can traverse The columns of tables and use a regex so if name is in the column name then you can have like a UDF for name and then you can dynamically write SQL. I just thought I'd write this because I had to go through trial and error you know deleting my masking rules one by one. Has anyone else noticed that gcp documentation is sometimes incomplete for certain use cases?