Marketo Migration to the Adobe Admin Console - Post-Migration

Transcript

Hello, everyone. Hello and welcome. Thank you guys for joining today’s tech sessions. My name is Jordan and just a couple of housekeeping notes before I let our presenters take it away. We encourage and hope you ask questions throughout the presentation. In the Q&A chat, available in the right corner where the presenter is speaking. However, rest assured that the last five minutes of the presentation or so are dedicated to just answering your questions. Additionally, a link to this recording will be emailed in about 24 hours and will be available on Adobe’s Experience website. Should you wish to view it again or share it with some of your colleagues. I’ll give this a second. If cases. Any questions? All right. Well, perfect. If there’s no further questions I will go ahead and pass it to our presenters. Good luck and enjoy everyone.

And good morning all. Okay. This is what we’re going to be talking about today. It’s actually going to be on Experience Cloud. And basically what happens after a post migration. So to introduce the team anyways my name is Kari Nelson. I’m a lead for, for support. I’ve worked actually for Adobe for 15 years. And, most of that’s been on the album console. And joining me today as, as a co-presenter, who you’ll be hearing from is going to be Justin. Justin’s actually worked with Adobe for 3.5 years, and he’s one of, One of the, leads. Anyways, that is on my team.

And joining us, actually, that’s going to be handling our questions is going to be, Taylor. And also, I believe Zach is also going to be helping out, answering questions.

And the agenda today is going to be as follows. So we’re going to do a overview. And then what we’re going to do is I’m going to pass the baton over to Justin. And then I’m going to do a presentation anyways on moving forward.

Excellent. Thank you. Okay. So we’ll move over to this next slide. So now that you’ve migrated your Marketo to the admin console, what now? So first let’s remember the goal of the admin console. The admin console is meant to be a central location for managing your Marketo users, your admins and your identity. This standardizes the way you manage Marketo to align with all your other products that you may purchase from. I know now that you’re onboarded to the admin console, you have Adobe’s Enhanced Security, streamlined workflows, and access to all of our, latest and greatest features and features that will come out with you in the future.

So I want to start with day one, and prepare you for helping your users demo the new login experience. Talk about accepting the invitation to your Adobe org. If your, users utilizing Adobe ID and submitting support cases being a new experience, which is, moving from nation to experience me, give me one second, I’ll get my screen share.

Okay, so, first of all, I’m going to start with demoing, just signing in with my company ID so that I can you know, over the different account types here at Adobe. So, bear with me here because not everyone is going to see the same screens. So I just want to go through all of the all the possibilities here. So, at the very top, you see personal account and this corresponds to our Adobe ID. So for those of you who have not set up SSL for your Marketo and you have moved into the admin console, your users will be using what’s called an Adobe ID, and they will come to the Adobe login screen. They’ll give us their email address, they’ll continue, and then they will give us a password. You do have the option to enforce MFA or not. The bottom option here. Company or school account corresponds to our federated ID. We’re an SSL user. So those users would come to Adobe, give their email address, it be, continue button and they would go to your, SSL, providing that you’ve set up prior to your migration. It is if you have added your users as only an Adobe ID, or you’ve set up SSL prior to your migration and your users are added only as a federated ID, your users actually won’t see this screen. They’ll just have one option so they won’t have this screen. But if you did set up, Adobe ID for your users first and then have to migrate to. So later you would want to prepare your users, for which option to kick. If I have distilled this down into one statement would be when you add your users to Marketo in the admin console, take note of what the identity type is. That will tell you how they’re going to log in. A Covid again, is that username and password experience Federated ID is our SSL experience. So I’m going to swap over to the another window where I’m actually already logged in. So I want to demonstrate two things here. First, when you tell your users to come to experience.com, which is they, you know, for best user experience support suggests that all Iinet’s customers direct their users to log in at experience dot dot com. This is the the easiest flow for your users going forward. When they get logged in, they’re going to have a, a marketo engage button where they can click. They’ll have their, their Marketo environment that they can launch. If you had one, 2 or 10 environments, all of those would be listed right here. Once you launch into Marketo, you would have a, an option to swap between those different organizations. Yes. Or there’s different Marketo instances. Excuse me. Yes, those were available. Now let’s say you are a customer and you have more than one experience. Cloud organization. And to speak about that use case a little bit, sometimes different departments in a larger organization will buy different contracts. And in that scenario you may be in more than one Adobe Org or Adobe Admin Console. If that is the case, you would just be able to pick up here at the top, between the different, Marketo or different experience cloud organizations that you have. Swapping is easy. You just basically click and you will come to the other organization. I purposely don’t have Marketo engage in this org because I wanted to show one quick, error that we see a lot.

You see, I swapped organizations and I was kicked out of Marketo because for Marketo. Engage. Excuse me? Because this organization doesn’t have it. So just suffice it to say, make sure your users know which or has which product. Again, it’s only applies to customers who have, Marketo or or. Excuse me, who have experienced old products in different organizations.

Now I would like to jump over to the new support process really quickly.

The the new URL for support is basically experience lead directory.com. So if you come to the lead you would be presented with this screen. You click support at the top. You would again this user is in two different organizations. So they’re going to have an org anchor here. So they would need to know which organization to submit their cases under. Once picking the correct org you’ll have the option to select different products. You see here that I, have Marketo engage. And this is a topic that Carol would hit on a little bit more in a second. But I have that because a specific role in the admin console, titled Support Administrator or a product support administrator, sorry. So that’s a new role in the admin console. And that’s the way that you assign your authorized support contacts for Marketo Engage. You also have the opportunity to pick specifically this is just an admin console issue. So I’ll go to the ticket submission process really quickly. You would have to give the, the case a title. Have a specific one to tell my team just to discard this case. And I’m going to submit this as a live. It’s going to go pretty quickly. This is recorded so we could go you can always go back and reference this.

If you’re putting in a marketo engage case, you would be able to pick between the different, issue reasons, which is basically telling us which team to send the case to. We’re going to take that admin console for now. So it comes into my case and we’re going to make it a P4. But certainly evaluate your, cases urgency and let us know, that urgency and that in fact I’m also going to just take the phone number. But definitely if you’re going to put in a high priority issue, give us a real phone number so that we can reach out to you can also give us some extra details here and or excuse me, you can also give us some extra emails to keep up to date on the case here, and add any attachments that you would like. Once you submit the case.

You can go to the my case view and you can see all of your open cases, closed cases or cases open that others in your organization. That’s pretty much the support process. And I’m going to go through one final important point.

I mentioned the Adobe ID earlier. So just in case you are not using SSL and you are using Adobe IDs, there is an additional step for your users to get, their accounts activated. We just want to go through that really quickly. So I’m going to demo setting up any accounts. So bear with me just one second while I receive this. You know, to confirm my identity. So that first step is users come to log in, they’re going to get an email that they’ve been invited to an Adobe organization. They have the ability to click on the email, but even if they don’t get the email, that’s not a blocker for them. They can just go to experience.com like any other registered user. They will be presented with this screen to say, hey, we need to confirm your identity. We’ll send them a one time pin, once they can satisfy entering that and we will allow them to, set up their account.

So I can get one that it likes right off the bat. We do ask for the month and year of their birth. We don’t really care what your actual birthday is, but I. We do need the account to be, an adult. So just make sure you pick something that makes the, the account over 18. Once you click complete account, we will take you in. And that’s pretty much setting up the account.

It is very important if you are challenged to, join the team that you direct your users to join the team. An Adobe ID is an end user owned account, so we do require them to opt in to the account. I had previously set this up to make sure this is going to work, so I’m opt into the account, already. But just make sure that, you restructure your Adobe ID users to, to make sure they accept the invitation if you’re already set up on. So this is not something that you have to worry about. You’re using it for what it’s called, a fully managed account. And you can fully control those accounts. So now I’m going to, turn over to Karen. There’s my lead and our minutes. We’re here. So, give me one second. I’ll get the deck, reshare, and I will turn it over to you. Okay. Awesome. Okay, so I don’t know why that it wants to go all the way over to 13 for some reason. Go figure. All right, so what happens next? Okay. So let’s talk about that. So after after we have, now that you’ve seen at least like what’s kind of going on there. There’s different pieces anyways of moving forward with the admin console. So with the admin console, there are different roles such as product system and support. We’re going to also go through an understanding of a brief understanding on what, the identity types are, how to add remove users. We’ll cover SSL, in general. And then what we’re also going to do is also cover the, certificate updates. So which is going to be a yearly thing that you may experience if you’re a system admin. So first off let’s talk about basically the roles inside of the admin console. So the large role which basically can see everything across the top, is the system role. That means that you have full access to all the settings. The next role that we have is the product admin. What this is designed to is it’s going to be the role that basically manages the product. So when migrating from Marketo into the admin console, that means that the users, or at least the admins that work system are going to be made a product admin. And so that means that they have the ability to add users to the products and, manage stuff from there. With the profile admin, which is the next level below that, they can only manage just a specific profile within a product.

So, sounds like there’s some might be some trouble seeing the slides.

Hopefully give me actually a, a thumbs up anyways. Or, if you guys are able to see the slides.

Okay. All right. Awesome. Thank you. Okay. So in the the next role anyways that we have, the, the next role is actually the support role. And so the support role like Justin mentioned, is meant to, be what the, way of actually submitting tickets actually to us. Okay. So now let’s jump over to, removal. Anyways, of the or at least adding users. So basically adding users to the admin console anyways is pretty basic. So in this case anyways, with the screens that are on the slide, what we do is you go to the admin console, you’re going to go actually to Marketo, engage underneath products, and then you can click on the Add user option okay. And then you enter in the users information. And that allows you to add a user. So removing a user this is only again going to only just remove the user from the product. So downstream effects anyways inside of Marketo as an example is going to deactivate the user account. So removal process is basically the exact same. So you’re going to go inside of products and then go to Marketo engage. Once you’re inside of Marketo engage you’re going to click on users and then search for the user that you’re looking for. And then select the remove. It’s going to give you a prompt and tell you anyways like are you sure you want to do that? And that will remove the user.

So the next section anyways that I’m going to cover anyways is adding admins. So adding admins is also going to be the same kind of process.

So removing the the user, or at least the admins. Anyways. So you can basically remove a from the user section. So what this does though, just to clarify. Anyways, removing users, if you fully want to remove actually a user from the admin console, you would actually have the system admin actually remove it. So just specifically these slides anyways, that were put together were actually meant to remove users from the product itself. And so same thing. Anyways, for removing an admin, the admins basically will just remove the admin just from that specific product. So you go to the product, which in this case would be Marketo, you would select admins, remove the admin, and that would actually remove the admins access, which then trickles down inside of Marketo and removes some. Actually, as an admin.

Okay, so now let’s get into the identity types. So Adobe uses basically three identity types which is the Adobe ID, then the enterprise ID and the federated ID. And so the Adobe ID is basically meant to be like a personal account. So generally like if you’re buying things from Adobe or you’re a freelancer, you would actually have the Adobe ID. When an admin console is actually put together, you are normally invited as a Adobe ID, so you have control of that username and password account.

And so the next section there is going to be the enterprise ID enterprise IDs are basically controlled by the company okay. Or business and does not actually use SSL. Now the federated account is what we do use for single sign on. So that’s the company’s SSL.

Okay. So let’s get into like single sign on. So in order for you to do single sign on or at least set it up in your admin console or even do a trust to it, the single sign on process, you basically have to create a directory. The directory stores the information of your connection that you’re going to be doing. So that’s going to be underneath settings identity directories. And then you give it a name. So whatever it is you want to call it. So single sign on or Octo or whatever. So at least you’ve got some sort of friendly name. Then from there, once that you’ve entered that information and then what you do is you select the type of, of connection that you’re going to make, whether that’s going to be Okta, Azure, intra, etc. and then depending on that, it’s going to have setups.

So then you’re going to save it and then you’re going to add in domains. So that’s here’s basically what that kind of looks like to the rest of that process. So in the on the left is basically adding the card anyways for the SCA. So you can take the card anyways to the right is going to be up at the very top is basically what you’re going to see for adding the configuration. Now the most common is actually usually either Azure or other Saml and our other HTML providers, which would be Okta or Ping Federate. Those are at least the things that you would use. Or if you’re using Intro or Azure, utilizing Saml two, you would also use the the other Saml providers option. And then the lastly what we would we would do is the adding of domains. So Adobe does have to do a domain.

So next. Anyways after actually adding the domain anyways to the system, then you can actually run the test and make sure that everything’s working correctly. Going over to certificate renewals now. Right. So at the end of the year, or at least when the certificate actually, if it does actually expire, it’s usually going to be about three years or so, depending on like how aggressive it’s set to renew. Sometimes they don’t need it. But here is basically the process. You’re going to go into the admin console. You’re going to go into Settings Identity directories, locate at least the one that you need to change. And then from there you’re going to remove the meta data file at the bottom. Once you remove the metadata file, then you’re going to upload the new file that you would get from your IDP team and then hit next, next and save. So those screens on for that next section here. Then the first next is actually going to be for the auto account provisioning which is basically jumps into domain enforcement, that kind of thing. Or at least some of the other features that you can take advantage of, such as like zero touch administration.

And then the, the one after that is our certificates. Okay. All right. So let’s talk about the gotchas really quick. So, there are a bunch of them that are kind of out there anyways. So number one, if the Adobe ID needs to get invited, so what we mean anyways with this is like if a person is invited to the organization, then they need to go out to accounts.adobe.com and basically finish filling out their information, accepting that invite that they get as well as to the Marketo instance, and also making sure that they’re invited to that console. Okay. The next one anyways is like what Justin mentioned anyways is ensuring that you have also the same identity types in each of the consoles. That means that if you have a user that’s basically in the Adobe ID and then another one that has a federated ID, they’re going to have a login logout experience, which is not going to be very user friendly anyways for those users in order for them to log in.

The other thing anyways that also happens is it’s basically as well as having that same identity type on all the products. So what we would recommend anyways is like if you’re going to use federated IDs, use federated IDs on all of your consoles. If it’s going to be Adobe IDs, then obviously we have to make some exceptions, etc… One of the bigger things that we see from a support standpoint is how people, are able to submit a ticket, and that requires actually having the support admin role, which is a net new requirement, that we’ve had for the last six months. So even system admins, actually, if you’re going to be submitting anything on the experience league needs to also actually have the, role.

And then the last one anyways, that we commonly see is, hey, we’re having problems with logins. One of the biggest things that can cause that is actually ad blockers, especially like getting into the IBM console or even into products.

Okay. And with that, I’m going to go ahead and open it up for questions.

So Justin, if you wouldn’t mind joining me, let’s see what kind of questions that we can answer.

Quickly. So one of the is it’s screening through some of these, we had a question on what as a supplement. And I think you answered that already. But just for the groups that single sign on, that just means instead of authenticating against Adobe servers, we are sending or users because of the federated directory set up for sending your users to, a third party identity provider, be that Okta, Microsoft interacting Federate or something like that. Let’s see.

I saw a question. I can’t find it right now, but I did see a question about you. Can you set up SSL only for Marketo? So acesso is a global setting. You would set it up on a domain, when you set up. So if you have some existing users who are non SSL users, so they’re on an Adobe ID, you know, they don’t automatically get changed over to a federated ID. There is a conversion process that you would use BSD so you could, you know, set up. So change one Adobe ID over to a federated ID and test it out.

Which is something commonly anyways, that we do and especially like doing the, the checks and balances that way, especially for like making sure that it’s actually working. And then at that point anyways, depending on how many users that you have will basically then, you know, show you least how to convert the rest of the users via that CSV. Is usually that, if it’s about 500 users, for those of you that are system admins, give or take, that usually takes, what would you say Justin about maybe 40 50 minutes anyways to convert users? Yeah, that’s a pretty good estimate. So generally 500 users is a safe set of users to use for that, for doing a conversion like that. So you want to break them up into to about 500, so it’s at least manageable anyways, especially if you have like large groups of users. All right. So let’s move on to our next question here. This. All I did want to touch on one other thing. On the on setting up SSL, that I’ve seen a few small questions that seem to a little bit the same thing. If you set up SSL for a user, all of their products in that admin console will authenticate via SSL, so it’s per user. If you have Marketo engage in ADP and, you know, analytics or other products in that console, that user is going to change the way they sign in for all of those products for them. And, do like I see, we would like to use SSL. We have a mix of Federated ID and Adobe ID users. How do you switch the identities from Adobe to Federated? We do have I think Taylor is actually replying to that. We do have a CSV conversion process. You basically download the CSV file, we’ll fill out the required columns, and upload that file. Whoever’s in the file will get changed over. So if you only wanted to do one you’d put one in that file, and etc… Now I do see that question. Anyways, from Shane, you had asked about the IMS portal. Anyways, that’s the experience. Like replacing the Marketo Nation. That is correct. So once you then migrated actually over from from Marketo actually into the admin console, your cases, then at that point any of the ticket flows are going to actually go through the, the experience leak section. Anyways to submit a ticket. So if you need a backup copy anyways of any of your support cases, you can reach out to support any ways to obtain that. And I guess it’s worth mentioning that the community portion of nation still. Yes, yes it does. That’s right. Yes. For the yep for the foreseeable future. Right now, I don’t think there’s any plans to take that away, at least right now. Absolutely. Yeah.

All right. What else? So, Terry, I’ll give this one to you. I think you hit it earlier, but, tomorrow to ask, can you give any examples of common lockout issues? Outside of the listed gotchas. Common lockout issues? Let’s see. Well, the more common ones that we’ve seen, a lease on common lockout is. Well, number one, if you’re using an Adobe ID that’s forgetting your password. So the the system anyways itself when you log to, experience started to become or on to experience league or even adobe.com the the system anyways that you forget your password will do a soft lock of about 15 minutes and so obviously resetting your password and making sure anyways that you’ve got access to your phone actually is helpful for that kind of thing. For SSA. So the common lockout will be your network password, or at least obviously not belonging to the application is another great one. That’s that’s one that we see. It’ll say something like, something has happened. It contact your IT admin. It could be at least a couple of things either not having access or it could be that the SSA configuration has been changed over to use the UPN or. And so if it’s using the UPN, for Adobe, that translates to the SSL username field. And so if it is different in the admin console, that’ll also cause a lockout as well. So we’re users can’t log in. Justin, is there anything else you can think of at least on that one? The one thing that popped into my head is, if, you know, a common scenario that we see is, users who are now in an admin console because they’re assigned to Marketo previously were in an admin console and assigned to Acrobat or Creative Cloud. And so we kind of call those cross cloud users. And those contracts are often purchased by separate, groups inside of your organization. So they ended up on, different consoles if you’re going to set up. So for Marketo, you want to look at that, Creative Cloud console as well, and make sure that you convert the users over there to federated IDs. Also we have a functionality called a directory trust that you can kind of, join those two consoles together from the identity perspective. And so just an easy way to say it, we want all of your users to sign in with this same account to all their products. We wouldn’t want Creative Cloud on an Adobe ID in Marketo on Federated ID, because you just confuse the user experience on how they should be logging into their Adobe products. Okay, now I see that there was a question. Anyways, that’s interesting to me. Anyways, for Adobe Experience platform or AP, AP itself. Anyways, it is actually broken into two different sets.

So if you do actually have users that cross from Marketo actually into AEP, the way that the system operates is that the user has to belong to a default, profile, which is referred to as like a default. And then the rest of the granular permissions, if you will, is actually inside of AP itself. But you need to make sure anyways that you have specific roles and etc… AP team also does have like an article. Anyways, on that, that kind of explains like login problems. So if you’re having issues anyways, with AP for login, feel free to submit a ticket. Anyways, to support them, we can pick it up from there and go take a look at it.

And see what else do we got here? I saw I see this, Christine. Previously we could set up roles in workspaces when we edit users in Marketo engage. How do we access those same roles from the admin console so that P stays in product? Marketo. Correct. As far as the admin console is concerned, the console knows that you have access or you do not have access to Marketo. And it knows if you’re that top level administrator because you’re assigned to that product profile and you’re because you’re assigned to that, product administrator role. So, you’re either in or out as far as Adobe Admin Console. And so those fine grained permissions, are still inside of the products. I shouldn’t be impacting. So if you’re saying something different than that, Christina, you need specific help on that. Feel free to put in a support case. And we’re happy to, to look into that.

And it looks like there was a follow up question to Zach’s, pre migration piece. So if you press the getting started awesome. Okay. The prereqs anyways making sure anyways that you’ve gone through those. Yes. Single sign on. I see Justin already answer that it is required. Just if especially if you use. So actually inside of Marketo we would like you to actually continue to use Essa. So in the admin console, is the thing, at least for that. If there’s anything else more specific anyways, on that one, let us know.

Is it possible to remove a marketo product from an SSL account that has been inactive for a defined period of time, like not logged in 90 days? If you mean automatically, we don’t have an automatic way to currently. So just say if a user hasn’t log in and on the 91st day or some configurable range, you just automatically turn them off. You if you set up SSL, you could define that from the identity provider.

If you would like to request that, you can certainly put in a support case and we can put that in as a feature request and see if the development team is willing to take that on. You know, to add to that as well. I know that there are some companies that also use ServiceNow. And so ServiceNow also would track something like that for like logins or like last login etc… And so you can define it inside of ServiceNow at least that way. So I’ve seen other clients, get away with it with using it that way for that. But as far as anything else, from a console perspective, we don’t offer that.

So to review the SSL certs moving forward for like who actually handles that one? If that’s the the SSL cert that’s inside of Marketo, it’s still actually is like lives inside of Marketo if it’s the ones that are actually utilized for, analytics that goes through the analytics team. And if it’s the other cert set that actually goes through, admin console, then that would be like the meta file. And then basically that can be managed by the system admins and your internal IT. So generally and they’ll do like a cert renewals at least on those.

Shown you would need to be a system administrator inside of the admin console to access the identity screen at all. So for setting up SS over, renewing a cert later for making any changes to the integration, same root system admin in the admin console.

You have to change expand the role. So just as a concept, if you have an administrator role inside of the console, you can give that role to another person or any role underneath it. So if you are a system admin you can promote another system admin. We don’t have a concept inside of Adobe and of a limit of admins. You can have, you know, technically everyone could be a system admin. We probably wouldn’t just assume, kind of open it up to too many changes, but yeah, Yeah, at that plenty of ways. That’s just unruly. Yeah. The the most that we’ve actually seen is, Gosh, what was the Justin like close to like 50, I think system admins on a console. So the thing is, is like with this one is like, make sure that you’re working together. If you have like a whole lot of system admins and you set clear and concise boundaries, especially if there are multiple now the main way that you can tell if you have the system admin rights, if you’re not sure, is if you can see the settings tab, up at the top in the black bar, then you actually have system admin rights.

Exactly. What is meant by product profiles? That’s really the Adobe word for product license. And so if you want to assign a user to Marketo, you would come in to the admin console, you would click on products and on Marketo Engage and you will see that there is a, product profile under there, kind of functions the same way as a user group. You add users to it and then a the admin console would provision a user, inside of the product. And see within a standard upload template for users within the admin console, three columns appear to be to username email address. And I’d happy question. Okay. So if you’re meaning just to add user style, an Adobe ID would always have the same username as an email or team manager. The admin still always have the same username and email address value, but that may not be the same for a federated IP. There are different ways to set up SSL and what you would use is a key identifier. Some users say you were using Microsoft. Some companies would have their email address as their email and their user principal name. But some may have some specific, employee ID as the UPN. And if you wanted to use that as your key identifier than that username in that file would need to be specified to be that, and whatever that value for that UPN is, and I’m not sure what you mean about the ID field. The only ID field that comes to mind is the inside, which would be a numerical value. So I don’t think that’s what you need.

Yeah. So, Yeah, that numerical value anyways itself on the ID field is not necessarily needed.

At least not in the edit user space by CSV identity method. Usually with that anyways, you usually only have like the Adobe ID, on the first column, the email address for like the username and then followed by the email domain, and then the identity that you’re moving to, and then followed by basically the the new username and email address, which would generally be like the same like what Justin mentioned, unless you’re going to actually change like the username to like basically like a UPN or something like that, or like employee ID number or something like that. And then the last column anyways, that’s on the template is the country code. If you forget the country code at all, it will not work. So you need to actually have the country code filled out as either the two letter code or use or which would be undetermined in capital letters. We do actually use the country code if for Creative Cloud products for Experience Cloud, it’s not utilized as much. So just kind of keep that in mind. So we would prefer do you’d use the the appropriate country code. So if you’re not sure what it is, export the entire list of users in the console using the three little dots export users. And then you can get actually the country code that’s on it okay. So see what else we have. So I see one about system admins. That’s the admin console team here at Adobe. And support does have the ability to promote system admins in your console. We do try to do that as a last resort. So we would encourage you if you have some existing admins that create a process that they’re going to leave the company, they would first promote, a replacement. We totally understand that sometimes that doesn’t happen because of the way someone may leave the company. Just put in a support request. And, we will take the internal steps that we needed to verify who you are and that the request is legitimate. And yes, we can, with a support case, promote a new person to the system. I’m in role. What else do we have? Well, to add on to that as well, Justin is like, the main thing is, is like, if we have an admin anyways who has left the company, we need to be able to verify anyways. You know that, like that person actually has left and that it is the the contract owners wish that we promote a person. So like like Justin said, it’s pretty much like last resort for us to do it. But yes, we can’t do it.

Jose, eight years. The explanation that you just gave it the two consoles, one for marketing tools and one for, Creative Cloud, if you wanted to put in a case with the admin console team, we can definitely take a closer look. But at a high level, we have what’s called a directory trust that would kind of join those two consoles together. I see you mentioned a sync. We also have a functionality called the Global Admin Console, which would allow you to extend that sync service to the other console. That way you don’t have to disable it and add someone manually. You can have a more, automated, user management process and use that sync on both consoles, potentially. We’ll have to take a, yeah, a look at your specific consoles because sometimes there are some, some challenges to that. But I would encourage you to put in a, an admin console case and just lay out both of the org IDs, and we’re happy to go through with you.

Yeah, most definitely, at least on that one if you’re also using the org to assist. So user sync from user sync tool as well. That could also disable that user account. But yeah, put in a support ticket. We’d be happy to look at it and see what we can do at least on that one. So with the this one anyway is about the first and last name missing. Anyways, if they are missing and it’s a federated user, then how that needs to change is wherever the domain claim is. So if that’s actually on the console, where the domain has been claimed as well as Marketo exists, you would just go underneath users directory users and then make the adjustment. At least from there, if sync is running, it should have picked it up. If it doesn’t, you can. You’d have to have the system and pause the sync. Go into the directory users underneath the users tab, and then edit the the first the first name and last name filled with the appropriate information. And then save the record. So it always has to be done where the domain is claimed at. If you’re trying to do that on a trust, it will never update.

We sometimes see that one a bit as well.

I’ll add the same comment if you’re having trouble with that, throw in a support case. We’re happy to to walk you through best practices. Yep.

Yeah. No more. Correct? Yeah. Can you tell us more about user groups and the reason for these user groups? It was a very interesting concept anyways, that Adobe actually came out with about, I want to say like eight and a half years ago. The idea was to group users into a specific set that actually would utilize a certain set of tools. And so it was meant actually for deployment, the way that that it gets used now, a lot of the time anyways, is actually with user sync. So with users sync, the users sync, ad group or Active Directory group gets synchronized from Active Directory to the admin console. And so when it does that, it turns into a user group. Now user groups could be considered something that’s called like a local user group, which means that it’s in the console. You manage it in the console. If it’s a group that’s being managed by Active Directory, it’ll have two arrows that are pointing in opposite directions, meaning that we’re synchronizing it. And so, depending on basically usage, you can apply up to, I want to say the, the limitation on that is about 14 product profiles on a user group. So you can you can do a lot of damage or a lot of good, depending on how you want to look at that. With the user group.

Hopefully that answers your question. If you if you have more on that one, let me know.

Is all the questions I see currently if we missed them and you want us to answer them, you don’t mind pasting them again into chat. Yeah. Your question may have gotten buried. If we’re not seeing it.

Yeah. And and that’s the other thing anyways, which is can be a little bit hard if you are actually the product admin dealing with Marketo. I see the last company was about directory sync unknown and and is it’s system admin only. So you really can’t see it. You really need to actually get connected to your, your system administrator and have a discussion with them on like what’s going on with those settings. Because yes, you are correct, you would not be able to see them as a product admin. I just actually took a call today from another client that had the same exact problem where they’re like, we have 6000 plus users and we’re only seeing about 558. And so it became pretty evident anyways that the, the whole thing that actually went to quarantine, with when quarantine happens with Active Directory sync or skim, obviously it’ll pause that. So you get this little red blinky error message that’s in the console that basically says an error has occurred. And then in order for, us and support to troubleshoot that, we have to have you look at your provisioning logs inside of Azure. And so we need basically those Azure logs to tell us exactly what’s going on with the problem. So if you see problems anyways where you’re like hey, the user’s not showing up and you know for a fact that your company synchronizing, you want to basically reach out to your IT support and get them on the phone with us. Okay. Say one more from Christine, Okay. So the reason that you see the user is under your business ID directory, even though your directory, even though you remove them from the user screen. So when you add a user to the admin console, you’re actually adding two accounts. You’re adding a business ID and you’re adding up an authentication account rather that’s, the Adobe ID of the Federated ID or the enterprise ID on the user screen. What you are seeing are business IDs. Those stay in the business ID directory, because of what’s called, enterprise storage model. This really doesn’t help or give a lot of benefit for you in Marketo. But if you did have, Creative Cloud or Acrobat products and those come with cloud storage, and that’s a way for us to preserve that cloud storage, if you’re just removing that user temporarily for a troubleshooting step.

And also if they were to leave the company and they had some valuable, you know, assets that they had created and you delete them or that user sync or whatever automation you have deployed users out deletes them. Instead of us purging that data for good, we put it into kind of a recycle bin. That way as an administrator. And it wouldn’t it need to be a system administrator role inside the console. You can come and get that data, download it and see what it is, assign it to another user or when that user is added back. If you use the same email address you will link back to that. So it’s a little bit of a creative cloud. Acrobat or kind of cloud document cloud concept, is the reason you’re seeing those. If they’re off of the user screen, that means they don’t have any entitlements or any admin roles. So they’re not going to maintain access. So it’s not that they can still get in. It’s just it’s maintained to preserve potential cloud storage.

And the admin console for about an option to remove a user who left the organization so manually. Yes. If you set up, some type of automation as far as our user sync tool, if you have some system that can make API calls to our you Matthew platform, Matthew just means user management API. And or if you have some ability through your Microsoft Azure or intranet, to set up a skin sync connection. Those are options that we have to automatically remove users based on some configuration that you change in your identity provider. We do not have some automation that would remove those users, know, like they haven’t logged in in a certain amount of time. But certainly if you set up so in user sync, we can key off a user group membership or the fact that the account is no longer active and it becomes disabled in the federated ID in the federated directory and no longer have that access. And it would disappear from the user screen, you would reclaim a license, etc…

I think we’ve ran out of questions. I think we might have. We have about five minutes left. So anybody has anything else? Feel free to throw it in. Or if we given an incomplete answer, ask us a little bit more and we’ll try to explain a little bit better.

Okay. I think we’ve exhausted all the admin console stuff. Scary. Okay. Sounds awesome. Well, thank you all for being such good audience today. We really appreciate it. Happy to, answer questions. If you do, you want, us to do more, presentations like this or be able to do rapid fire questions, we’ll be more than happy to also work with teams anyways to set that up. So express requests anyways on that. But yeah, we appreciate your time today.

Okay. Perfect. Thank you guys. Thank you for such an informative presentation. And thank you all again for joining us for Tech Sessions. Just a reminder, a link to this recording will also be emailed in about 24 hours and will also be available on Adobe’s Experience League page.

And we hope to see all of you again. Thanks, everyone. Bye.

Hi, guys.