Timeline for Does creating a child flow that is called from an automated flow create a security hole inside our tenant
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2023 at 11:13 | answer | added | Ganesh Sanap - MVP | timeline score: 1 | |
| Jul 5, 2023 at 11:12 | comment | added | microsoftdeveloperdesigner | @GaneshSanap also they can not use the connection and they can not use the workflow , am i correct? | |
| Jul 5, 2023 at 11:11 | history | edited | Ganesh Sanap - MVP | CC BY-SA 4.0 |
deleted 9 characters in body; edited tags
|
| Jul 5, 2023 at 11:10 | comment | added | Ganesh Sanap - MVP | then they cannot use it in their own/other flows | |
| Jul 5, 2023 at 11:07 | comment | added | microsoftdeveloperdesigner | @GaneshSanap no i did not share it with any other use | |
| Jul 5, 2023 at 5:57 | comment | added | Ganesh Sanap - MVP | Did you share the "SetPermision" flow with any other accounts than service account? If no, they will not be able to use it in their own flows. So, you should be good. Let me know if it answers your question. | |
| Jul 5, 2023 at 2:29 | history | asked | microsoftdeveloperdesigner | CC BY-SA 4.0 |