<blockquote>
  <p>I would really prefer to not have to also manage a separate Active Directory Domain within our VNets</p>
</blockquote>

<p>You've already found the answer: centralized authentication.</p>

<p>If you use a tool like <a href="https://www.okta.com/partners/gsuite/" rel="nofollow noreferrer">Okta</a>, you can <a href="https://support.google.com/a/answer/60224?hl=en" rel="nofollow noreferrer">indirectly tie GSuite to AD</a> (or an LDAP server).  And then of course you can <a href="https://serverfault.com/q/23632/12214">tie OpenSSH there</a> as well.</p>

<blockquote>
  <p>or deal with revoking ssh keys</p>
</blockquote>

<p>Centralized authentication solves this.</p>

<blockquote>
  <p>or updating multiple usernames/passwords on every single VM we deploy.</p>
</blockquote>

<p>And this as well.</p>

<p>You've already got the answer, even if you don't like it.</p>

CC BY-SA 3.0
2017-12-19T07:56:20.063Z
None of your links and nothing in your answer actually shows how its possible to use Okta to log into a windows or linux machine. It looks like Okta just syncs with Active Directory to let you log into apps.
avi
CC BY-SA 3.0
2017-12-19T08:51:16.937Z
@avi and then it's the usual matter of login with an ad account which is the replica of a g-suite account, pbis-open does this for linux, windows does allow login toward a windows Active Directory obviously...
Tensibai
CC BY-SA 3.0
2017-12-19T21:38:15.103Z
@avi I added a link to https://serverfault.com/q/23632/12214 which talks about that.
Xiong Chiamiov
CC BY-SA 3.0
2017-12-21T08:03:40.163Z
I'm still not understanding the answer. Will I need to maintain a list of Active Directory users, and give them individual permissions and logins, or will it just use the Gsuite credentials directly?
avi
CC BY-SA 3.0
2017-12-26T18:57:52.643Z
@avi You'd manage users in AD, and then Gsuite users get created automatically from there.
Xiong Chiamiov
CC BY-SA 3.0
2017-12-18T20:12:12.333Z
2017-12-19T21:37:52.603Z
2017-12-19T21:37:52.603Z
Xiong Chiamiov
<p>I want to manage the members of our team who are able to log into our cloud-hosted VMs, both Linux and Windows.  We currently use <a href="https://gsuite.google.com" rel="nofollow noreferrer">G Suite</a> and <a href="https://github.com/" rel="nofollow noreferrer">GitHub</a>, to manage access to our code and documentation etc. I would really prefer to not have to also manage a separate Active Directory Domain within our VNets or deal with revoking ssh keys or updating multiple usernames/passwords on every single VM we deploy.</p>

<p>Are there ways to use either GSuite or Github to control login access to our VMs?</p>

<p>If there isn't, what are the best practices to deal with 20+ developers who are all empowered with DevOps responsibilities?</p>

<authentication>
Using GSuite or Github to Manage who can log into Linux or Windows VMs on Azure
avi
# Using GSuite or Github to Manage who can log into Linux or Windows VMs on Azure

(Asked by: username_0 on 2017-12-06)

I want to manage the members of our team who are able to log into our cloud-hosted VMs, both Linux and Windows. We currently use [G Suite](https://gsuite.google.com) and [GitHub](https://github.com/), to manage access to our code and documentation etc. I would really prefer to not have to also manage a separate Active Directory Domain within our VNets or deal with revoking ssh keys or updating multiple usernames/passwords on every single VM we deploy.

Are there ways to use either GSuite or Github to control login access to our VMs?

If there isn't, what are the best practices to deal with 20+ developers who are all empowered with DevOps responsibilities?

**Tags:** authentication


---

## 1 answers

### Answer by username_1 on 2017-12-18. Score: 3

> I would really prefer to not have to also manage a separate Active Directory Domain within our VNets

You've already found the answer: centralized authentication.

If you use a tool like [Okta](https://www.okta.com/partners/gsuite/), you can [indirectly tie GSuite to AD](https://support.google.com/a/answer/60224?hl=en) (or an LDAP server). And then of course you can [tie OpenSSH there](https://serverfault.com/q/23632/12214) as well.

> or deal with revoking ssh keys

Centralized authentication solves this.

> or updating multiple usernames/passwords on every single VM we deploy.

And this as well.

You've already got the answer, even if you don't like it.

> **Comments:**
> **username_0**: None of your links and nothing in your answer actually shows how its possible to use Okta to log into a windows or linux machine. It looks like Okta just syncs with Active Directory to let you log into apps.  
> **username_2**: @username_0 and then it's the usual matter of login with an ad account which is the replica of a g-suite account, pbis-open does this for linux, windows does allow login toward a windows Active Directory obviously...  
> **username_1**: @username_0 I added a link to https://serverfault.com/q/23632/12214 which talks about that.  
> **username_0**: I'm still not understanding the answer. Will I need to maintain a list of Active Directory users, and give them individual permissions and logins, or will it just use the Gsuite credentials directly?  
> **username_1**: @username_0 You'd manage users in AD, and then Gsuite users get created automatically from there.  

---

