Transcript
Now, the evolution speed of cloud and SaaS has greatly exceeded the traditional protection model. Ears, Native Cloud Service, and SaaS, each has a different way of protection, which makes it easier for gaps to be filled. That is why the scope of support for recovery is necessary to expand in accordance with the shape of the cloud. Even if the workload and platform are different, it is important to keep the same idea consistent. I will introduce the extension features for Azure. In Team Data Cloud, you can protect Azure services in a full-managed, cloud-native way. The characteristic is that SaaS services such as Cosmos DB can be protected in the same way as other Azure workloads. Also, in Azure SQL, by integrating with Enter ID, you can run operations including ID management in a simple way. In addition, by expanding the support region and long-term support options, it is easier to balance versatility, performance, and compliance. About Microsoft Planner. Since the Planner is a Teams task manager, it is used on a daily basis, but it is also easy to leak data from backup targets. In Team Data Cloud, we plan to provide native backup to the Planner. Not only the Planner that is tied to Teams, but also the Planner plan that is used individually can be used as a backup target. In addition, not only the plan unit, but also the bucket and task unit can be used as a restore, allowing rapid recovery for real-time operations. By selecting Teams or a group, the related Planner will be automatically protected, so the number of operations will not increase. About the protection of the Enter ID itself. As I have mentioned before, the ID is the starting point of the attack. Therefore, it is important to protect not only the user, but also the ID settings and the policy itself. In Team Data Cloud, important data related to access control, such as access policy with conditions and Intune device settings, is also protected. In addition, you can restore only the necessary parts while checking the difference at the policy level. You can safely return everything to the correct state, not from scratch. Let's take a look at the compliance side. The recent regulations are not simply about protecting, but focusing more on restoring and explaining. In addition, as the expiration date is getting shorter, the pressure to prepare for daily operations is also increasing. It is important to think that the same data cannot be completed just by monitoring. In Team Data Cloud, the data collected in compliance with the regulations can be used to improve operations and make decisions, and insights can be drawn from this data. Compliance is not just a cost, but an advantage in operation. This is a feature extension for Salesforce. In Salesforce, business processes based on settings and metadata are important, not just records. In Team Data Cloud, both data and metadata can be protected and restored in a meaningful way as a business. In addition, you can search, display, and restore archived data without leaving the Salesforce UI. In addition, we also support the latest security requirements of Salesforce through the official API, so you can operate with confidence. Backup data can also be used not only for restoration, but also for investigation and analysis. I will introduce how to do this in a one-dimensional way. In Team Data Cloud, you can manage all workloads from SaaS to IaaS with a single interface called One UI. Even if the workload increases, the number of screens and operations will not increase. In the dashboard, you can see the information you should see every day at a glance, and you can check risks and problems at an early stage. You can also manage user access, licenses, and operations on the entire platform. This allows you to keep operations simple even when the environment expands. I will introduce the One UI of Team Data Cloud using the screen. What you are seeing now is the management screen of Team Data Cloud. Here you can manage various workloads such as Microsoft 365, Azure, Enter ID, Salesforce, and Bolt. By clicking on each card, you can move to the management screen of each workload. This is the overall dashboard of Team Data Cloud. Here you can check the status of each workload. In the current security situation, you can check Salesforce, Microsoft 365, and Enter ID. By adjusting the cursor, you can check which protection targets are protected. You can check various types of protection such as Enter ID, application, role, group, user, etc. You can also check which objects are protected by the right-hand side of the data protection list. By clicking on a session, you can check if it is a backup session or a listener session. We also have a filter, so you can choose a workload unit or a tenant and update the dashboard. Here you can check the activity status. You can also check the status of a backup or listener workload. You can also check when it started and when it ended. You can set the user and role to be registered here. By setting the user's identity, you can enter an email address and limit access. You can choose a manager or a listener, select a role, and assign a specified role to the workload. We have a console that can manage the whole thing in One UI. This is the next step. So far, we have introduced the concept of Beam Data Cloud and its main functions. If you are wondering what the actual screen looks like, you can try the interactive product tour from the QR code here. You can check the actual feeling of the operation at your own pace.
