Katja Anacker
My feedback
99 results found
-
16 votesKatja Anacker supported this idea ·
-
40 votesKatja Anacker supported this idea ·
-
29 votesKatja Anacker supported this idea ·
-
30 votesKatja Anacker supported this idea ·
-
13 votesKatja Anacker supported this idea ·
-
2 votesKatja Anacker supported this idea ·
-
3 votesKatja Anacker supported this idea ·
-
5 votesKatja Anacker supported this idea ·
-
2 votesKatja Anacker supported this idea ·
-
8 votesKatja Anacker supported this idea ·
-
4 votesKatja Anacker supported this idea ·
-
7 votesKatja Anacker supported this idea ·
-
4 votesKatja Anacker supported this idea ·
-
2 votesKatja Anacker supported this idea ·
-
9 votesKatja Anacker supported this idea ·
-
36 votesKatja Anacker supported this idea ·
-
4 votesKatja Anacker supported this idea ·
-
2 votesKatja Anacker supported this idea ·
An error occurred while saving the comment -
8 votesKatja Anacker supported this idea ·
-
3 votesKatja Anacker supported this idea ·
I agree, we have the same problem. We are using the "workaround" that all resource groups are private and if we are close to the rollout date, we are adding the location to the AD-mapping and make it therefore visible. But there should be smarter options in place.