Skip to content

Commit cb61d38

Browse files
authored
Update 5-secure-access-b2b.md
1 parent 0fd0559 commit cb61d38

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/fundamentals/5-secure-access-b2b.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ You can limit the organizations your users collaborate with (inbound and outboun
3636
To control access your tenant, deploy one or more of the following solutions:
3737

3838
- **External collaboration settings** – restrict the email domains that invitations go to
39-
- **Cross tenant access aettings** – control application access by guests by user, group, or tenant (inbound). Control external Azure AD tenant and application access for users (outbound).
39+
- **Cross tenant access settings** – control application access by guests by user, group, or tenant (inbound). Control external Azure AD tenant and application access for users (outbound).
4040
- **Connected organizations** – determine what organizations can request access packages in Entitlement Management
4141

4242
### Determine collaboration partners
@@ -126,7 +126,7 @@ Determine who can invite guest users to access resources.
126126

127127
* Most restrictive: Allow only administrators and users with the Guest Inviter role
128128
* See, [Configure external collaboration settings](../external-identities/external-collaboration-settings-configure.md)
129-
* If security requirements permit, allow all Memeber UserType to invite guests
129+
* If security requirements permit, allow all Member UserType to invite guests
130130
* Determine if Guest UserType can invite guests
131131
* Guest is the default Azure AD B2B user account
132132

0 commit comments

Comments
 (0)